Hehe, this one is ugly... The difference is just that we use the default auto incrementing integer primary key, and you use an explicit primary key. So SQLAlchemy think you'll insert twice the same data and prevents you to do so. In our case it doesn't (cannot) care because the value for the primary key is not given.
Btw: thanks for pointing this out. I knew our tests were somewhat broken but didn't realize to which extent :) I'll have to fix all this mess once and for all... On 4/5/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Thank you again. Now that you responded, the need for > objectstore.clear() looks rather obvious. I should have thought about > it. Nevertheless, why did the test_order_by.py example work but mine > didn't? It should have had objectstore.clear() also, shouldn't it? > > André > > > > > -- Gaëtan de Menten http://openhex.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SQLElixir" 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/sqlelixir?hl=en -~----------~----~----~----~------~----~------~--~---
