Hello list, while migrating from 0.2.8 to 0.3.0 I realized some changes in (error raising) behavior.
If you try to flush an object with a duplicated primary key and the object (the one that existed first!) is in your session you get a FlushError (previously you got SQLError). If you do the same with the other object not in your session you get a SQLError. If you try to flush with a conflicts due to an unique constraint you alway get a SQLError. Bug or feature? -- Cheers, Sol. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
