Here is what I just committed to trunk and will make up release 0.4.1 of Elixir tomorrow if no objection is heard until then.
- polymorphic defaults to True ! (Mickael Bayer convinced me that inheritance should be polymorphic most of the time). - autosetup defaults to False ! (mostly because the change below makes it even less reliable). >>> this will break *a lot* of code <<< The cure to the breakage is to call setup_all() after all your entities have been defined, and before using them. - removed one of the autosetup triggers altogether: there is no "fake" mapper registered in SQLAlchemy's mapper_registry anymore, so if you try to access, the class mapper directly (not through the 'mapper' attribute on the class), before the setup phase happens, it won't work. This was done because of a change in SQLAlchemy trunk (future SA 0.4.2) which broke that piece of code (which was a hack in the first place), ie without this change your entities using autosetup would raise an exception not matter what in SA 0.4.2. So instead of doing some even uglier hackery, I got rid of it altogether. Since those changes are quite important (even if involving very few lines of code), it might be wise to go for version 0.5.0 instead of 0.4.1. Thoughts? -- 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 -~----------~----~----~----~------~----~------~--~---
