T.R | Title | User | Personal Name | Date | Lines |
---|
1147.1 | Need union all view to see dbkeys | BROKE::ABUGOV | | Tue Apr 08 1997 14:56 | 9 |
|
Hi Don,
This assumes that it is possible to uniquely identify a row. If you
changed your view to a union all view (I assume you have a union view)
then you will see dbkeys. You can't use dbkeys in union views, you can
in union all views.
dan
|
1147.2 | Thanks - will report back | BROKE::GREEN | | Tue Apr 08 1997 16:04 | 11 |
| Hi Dan,
Thanks.
I think I'll have to revisit my test. Yes, I used a union view. But
now that I look back at the customer's mail he claims he did a union
all view.
Back to the drawing board.
Don
|
1147.3 | 100% correct | BROKE::GREEN | | Tue Apr 08 1997 16:11 | 6 |
| Dan,
Right as rain on the union all view.
Thanks,
Don
|
1147.4 | doc bug 476705 | BROKE::GREEN | | Wed Apr 09 1997 16:26 | 8 |
| Created a documentation bug for this. Bug number is 476705.
Mentioned that a DBI union view does have a dbkey length of 0. Our
doc says the opposite.
Also mentioned that if someone has imported an Rdb view into DBI then
you can also have dbkey lengths of 0. I mention this in the doc bug
because it isn't mentioned in the doc.
|