(Dashing off a quick reply, as I'm on my way out - I'll have a proper read and think about your message later. Thanks!)
On Friday, 10 January 2014 17:22:35 UTC, Kevin H wrote: > I don't think it has to be committed yet, it just has to exist in the > session. See below. > That's really good to know. > Because p doesn't have a primary key yet? I'm kind of guessing...but I > really think you need a pkey on the input object to merge(). > Yeah... The problem is the PK is synthetic and I don't (ever) know what its value is - it's generated by the DB/ORM. I'd only ever be able to query on name, so probably merge is completely the wrong thing to use. Thanks for all the comments. I'll rethink my approach and see how I get on. Paul -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/groups/opt_out.
