I'm using Postgres, by the way. On Aug 18, 1:27 pm, Oliver Beattie <oli...@obeattie.com> wrote: > I'm not entirely sure why this is happening… it seems to work for me > in nearly all other circumstances so I'm a bit stumped. Basically, I > have a declarative table which has a character field as its primary > key (it's not an ID which can be returned by the server), yet > SQLAlchemy is issuing an INSERT…RETURNING statement for it. > > The scenario that seems to make it happening is like this. I'm trying > to create a copy of an existing object, with a new ID. All the > attributes on the new object should be pulled from the old object > (which I'm doing through use of the iterate_properties iterator along > with setattr, getarre calls), apart from this primary key field (name) > which is a character field and will be something different. A relation > on the "old" object will be updated to point at the created object. > When commit() happens, I get an IntegrityError because it's thinking > the db will return it the primary key (even though I have explicitly > set it on the non-persistant instance). > > Is this a know bug or something I'm doing wrong?
-- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
