> Isn't it what does already Elixir? not really. Frankly, i dont know much elixir, just some impressions. elixir is sort of syntax sugar over SA, with very little decision-making inside. It leaves all the decisions - the routine ones too - to the programmer. At least thats how i got it.
This one hides / automates _everything_ possible - the very concept of existing of relational SQL underneath is seen only by side-effects, e.g,. the DB_inheritance types "concrete-", "joined-", "single-" table. It decides things like where to break cyclical references with alter_table/post_update; makes up the polymorphic inheritances, etc. Of course this is only the declaration/creation part (building the DB model); after that it can cover only small/simple part of the queries (model usage) - combinative possibilities there are endless. That's why u have plain SA stuff, once the "python function over object converted into SA-expression over tables" path gets too narrow. dbcook does not have assign_mapper-like things, putting query methods on the objects. it leaves all that to you. Although one day there will be a usage-case/example of some way to do it - once i get there. elixir is lighter, this one might be heavier - depends on how u measure it. more differences maybe - no idea, someone has to have time to try both (:-) ciao svil --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
