Return-Path: <bhalpin@collaborativefusion.com>
Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm
Delivered-To: mailing list torque-user@db.apache.org
Received: (qmail 26103 invoked from network); 13 Feb 2003 21:15:17 -0000
Received: from relay.pair.com (209.68.1.20)
  by daedalus.apache.org with SMTP; 13 Feb 2003 21:15:17 -0000
Received: (qmail 2522 invoked from network); 13 Feb 2003 21:15:20 -0000
Received: from unknown (HELO ?192.168.1.11?) (205.201.8.169)
  by relay.pair.com with SMTP; 13 Feb 2003 21:15:20 -0000
X-pair-Authenticated: 205.201.8.169
Subject: Re: AW: how to set the PK manually?
From: Bill <bhalpin@collaborativefusion.com>
To: Turbine Torque Users List <torque-user@db.apache.org>
In-Reply-To: <CPEFIEDDAHFNNCNLNJGJGEOPCCAA.mail@marclustig.com>
References: <CPEFIEDDAHFNNCNLNJGJGEOPCCAA.mail@marclustig.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailer: Ximian Evolution 1.0.8 
Date: 13 Feb 2003 16:15:00 -0500
Message-Id: <1045170901.11476.178.camel@bill.collaborativefusion.com>
Mime-Version: 1.0
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Marc

Just out of curiosity, have you tried setting idMethod to 'none' instead
of null?  I just remember that being an option and wonder if it would
make a difference.




On Thu, 2003-02-13 at 15:54, Marc Lustig wrote:
> Interesting enough I found this in
> BasePeer.public static ObjectKey doInsert(Criteria criteria, Connection c=
on)
>=20
>         // only get a new key value if you need to
>         // the reason is that a primary key might be defined
>         // but you are still going to set its value. for example:
>         // a join table where both keys are primary and you are
>         // setting both columns with your own values
>=20
> So obviously my scenario is considered a valid one.
> But I'm not quite sure where the actual decision is made if a new PK is
> acquired or not.
> Can some Torque developer please advise me why in my case still a new PK =
is
> generated, although I set it using setPrimaryKey() before?
>=20
> Marc
>=20
>=20
>=20
> > -----Urspr=FCngliche Nachricht-----
> > Von: Marc Lustig [mailto:mail@marclustig.com]
> > Gesendet: Dienstag, 11. Februar 2003 15:59
> > An: Turbine Torque Users List
> > Betreff: AW: how to set the PK manually?
> >
> >
> > Thanks Justin and Peter for your input,
> > my statement "TABLE B extends TABLES A" didn't refer to the
> > OO-terminology.
> > table A actually respresents a base-user. table B represents a
> > specific kind
> > of a user. So both tables refer to the same kind of object, the user.
> > Hence the PK of table B should reflect the PK that was created in table=
 A.
> >
> > So my schema (table B) looks like this:
> >
> > 	<table name=3D"SPECIALUSER" idMethod=3D"null">
> > 		<column name=3D"SPECIALUSER_ID" primaryKey=3D"true"
> > required=3D"true"
> > type=3D"INTEGER"/>
> > 		<foreign-key foreignTable=3D"BASE_USER">
> > 			<reference local=3D"SPECIALUSER_ID"
> > foreign=3D"USER_ID"/>
> > 		</foreign-key>
> >
> > Problem is still, when I setPrimaryKey(x) this PK will get lost
> > once I call
> > save(). torque generates a new PK.
> >
> > Q: Is there any other idMethod that I could use to tell torque not to
> > generate any PK when save() is called?
> > Or is the only way to add a regular PK and refer the USER-table by an
> > additional column linked by a foreign-key reference?
> >
> > Thanks!
> > Marc
> >
> >
> >
> > > -----Urspr=FCngliche Nachricht-----
> > > Von: Campbell, Justin [mailto:jcampbell@profilesys.com]
> > > Gesendet: Dienstag, 11. Februar 2003 00:21
> > > An: 'Turbine Torque Users List'
> > > Betreff: RE: how to set the PK manually?
> > >
> > >
> > > Peter -
> > >
> > > I would argue whether or not primary keys are auto-generated by
> > > definition.
> > > This statement is true of "identity" (SQL Server terminology used her=
e;
> > > a.k.a. AutoNumber, ID, etc.) columns. However, a primary key can
> > > consist of
> > > one or more non-identity columns (e.g. a varchar(50) value).
> > >
> > > Personally, all my primary keys *are* identity columns (as this makes=
 it
> > > easier to isolate the actual "key" value and eases changes to the key
> > > combination in the future), but this is not necessary (nor even
> > > recommended
> > > by some schools of thought in DB schema design).
> > >
> > > Just thought I'd clarify for folks out there as this statement may ca=
use
> > > confusion among the uninitiated.
> > >
> > > Best of luck.
> > >
> > > - Justin
> > >
> > > -----Original Message-----
> > > From: Peter S. Hamlen [mailto:phamlen@mail.com]
> > > Sent: Monday, February 10, 2003 6:22 PM
> > > To: Turbine Torque Users List
> > > Subject: Re: how to set the PK manually?
> > >
> > >
> > > Marc,
> > >
> > > My understanding is that you cannot accomplish this if it's a primary
> > > key.  Primary keys, by their definition, are generated automatically =
so
> > > that there aren't any duplicates.
> > >
> > > As Justin Campbell mentioned in a previous email, you might want to h=
ave
> > > Table B have a foreign-key to table A (that's how most of us accompli=
sh
> > > this.)
> > >
> > > The other option (if you're really talking about "extending") is to a=
dd
> > > the columns for B into table A - and add a "type" column that indicat=
es
> > > whether the object in the table is of type A or B.
> > >
> > > For example:
> > >
> > > <table name=3D"PaymentPlans">
> > >   <column name=3D"Type" description=3D"Annual or Monthly"/>
> > >   <column name=3D"MonthlyBillDate" description=3D"Only used for Month=
ly
> > > types"/>
> > >   <column name=3D"AnnualBillDate" description=3D"Only used for annual
> > > plans"/>
> > >   <column name=3D"AmountDue" type=3D"INTEGER"/>
> > >  </table>
> > >
> > > You can find more information about this in the "Inheritance" section=
 of
> > > Torque.
> > >
> > > -Peter
> > > On Thu, 2003-02-06 at 13:20, Marc Lustig wrote:
> > > > Hi,
> > > >
> > > > I'm creating a new instance (row) and set the PK to a certain value=
.
> > > > (I need to do this because this table B extends another table
> > > A, so the PK
> > > > in table B must be the same as in table A.)
> > > >
> > > > My defaultIdMethod is "idbroker":
> > > > <database defaultIdMethod=3D"idbroker"...
> > > >
> > > > And to make torque not generating the PK I set idMethod=3D"none":
> > > > <table name=3D"B" idMethod=3D"none">
> > > >
> > > > Problem is when I trigger save() torque still generates a new PK an=
d
> > > assigns
> > > > it. How comes that?
> > > > How can I make torque not to auto-generate a new primary key
> > when save()
> > > is
> > > > called?
> > > >
> > > > Thanks!
> > > >
> > > > Marc
> > > >
> > > >
> > > > -------------------------------------------------------------------=
--
> > > > To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> > > > For additional commands, e-mail: torque-user-help@db.apache.org
> > > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> > > For additional commands, e-mail: torque-user-help@db.apache.org
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> > > For additional commands, e-mail: torque-user-help@db.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> > For additional commands, e-mail: torque-user-help@db.apache.org
> >
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-user-help@db.apache.org
>=20