AFAIR the it only affects SQL generation - adds unique constrain to the table. It makes no difference for OM.
fedor. ------------------------------- Amicus Plato amicus Aristoteles magis amica veritas > -----Original Message----- > From: Skip Walker [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 10, 2001 3:03 PM > To: [EMAIL PROTECTED] > Subject: Torque: unique-column feature > > > > I can't seem to find any useful information on exactly how > this feature > is supposed to work. Is there any torque documentation that describes > 1) how this feature is supposed to effect the use of the Peer and > DataObjects. > > I'm guessing that when a column is declared unique, an > attempt to save a > data object that has column a value declared as unique will cause an > update to be performed if another row already exists in the table with > this value. Is this a correct assumption? > > Skip > > --------------------------------------------------------------------- > 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]
