great, thank you much. i wanted to know, in part, that i hadn't missed
something. i'm going to use the same serial and hope that values aren't
entered in the Id field (i won't provide a way to do it in my client app,
so it should be safe enough). but the extra security is valuable to me,
to cov
e
tables. that way, when i do a 'SELECT baseTable*' kind of command, i can
differentiate between two records. is there a way to do this, or could
this be considered a valid bug of some sort?
thank you,
jmichael
[EMAIL PROTECTED] writes:
>On Sat, 2 Jun 2001, J. Michael Caine wrote:
>
[EMAIL PROTECTED] writes:
>Add a unique constraint to t1d(id) and it should work.
ahh, great. thank you! (does this mean that the derived class' field's
data may be allowed to be non-unique? interesting. thank you.
---(end of broadcast)---
TIP
s is a bug (and i'm not wasting your time) and easily verifiable,
j. michael caine
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
