save_or_update() doesnt take any kind of primary key or unique key argument. no specification of anything is needed.
Sean Davis wrote: > > On Tuesday 13 March 2007 07:35, Sean Davis wrote: >> We are creating a database that will have a set of autoincrement primary >> keys on the tables. However, many of the tables also have one or more >> unique keys associated with them. Can we use save_or_update() (and, by >> extension, cascade='save_or_update', etc.) by specifying one of the >> unique >> keys rather than specifying the primary key directly? > > Tried it. Looks like not. Sorry for the noise on the list. > > Sean > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
