On Aug 27, 9:05 pm, "Michael Bayer" <[email protected]> wrote:
> Y3s wrote:
>
> > It seems that the child instances are not updated with the right
> > sequence number. Moreover, if I turn the parent's "id" column into the
> > primary key, the error disappears.
> > Is it a known issue? Can i fix it in some way (except for normalize
> > the db schema)?
>
> I dont believe MSSQL support free-standing sequences (only IDENTITY
> columns, which share some similarities). At the very least SQLAlchemy
> doesn't have support for them.
Of course, but since in some cases it works (if the IDENTITY column is
the table's PK), I cannot figure out why in my case it doesn't!
Thanks
Antonio
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---
