depends on your case. it may have another field for PK or use the
combination of those two PKs as it's PK.
Anyway, PK is always good :-)
fedor.
> -----Original Message-----
> From: Travis Low [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 10, 2001 8:43 AM
> To: [EMAIL PROTECTED]
> Subject: Re: doDelete without a primary key
>
>
> Jason van Zyl wrote:
>
> > On 7/10/01 9:20 AM, "Howard Lin" <[EMAIL PROTECTED]> wrote:
> >
> >>If I call doDelete on a table without a primary key, I got
> the following
> >>exception:
> >
> > Why don't you have a primary key? Are you using Torque to
> generate objects.
> > All objects that are retrieved/saved by Torque should be indentified
> > by an OID. I don't think setting up a system where your objects have
> > no OID/primary key is a bad idea. How are you tracking them without
> > a unique identifier. Or are you using something else as an
> identifier?
>
>
> If a table represents a mapping between two primary keys in
> other tables, should it have a
> separate field as a primary key?
>
> --
> -- Travis Low
> <mailto:[EMAIL PROTECTED]>
> <http://dawnstar.org/travis>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
