On Nov 16, 11:48 am, Gaetan de Menten <[email protected]> wrote: > ========== > Elixir is a declarative syntax layer and "database pattern framework" > on top of the `SQLAlchemy library <http://www.sqlalchemy.org/>`_. By > database pattern framework, we mean that it can automatically generate > tables and mappers and provides a way to express "development > patterns" which require some database elements (specific columns or > tables). These patterns can then be easily reused.
I completely agree with this description, but despite your explanation of the term, some people might be put off by the term "database pattern framework". I prefer Kevin Ar18's suggestion "It simplifies much of the boilerplate code from SQLAlchemy, resulting in code that is easier to work with and is cleaner to look at. Since Elixir is only a layer on top of SQLAlchemy, all of Elixir's core features come from SQLAlchemy." which I would re-word as follows: "It simplifies much of the boilerplate code you'd need to write (declaring tables and mappers) if using SQLAlchemy directly. As a result, your code, if based on Elixir, will be easier to work with and cleaner to look at. Since Elixir is only a layer on top of SQLAlchemy, complementing it, you lose none of SQLAlchemy's power by using Elixir." Also, if we assume that people using SQLA are familiar with entity relationships, then it might be better to just list the relationship types which Elixir makes it easy to define, and focus more on inheritance support, versioning and perhaps things like associable() - all which add some value on top of SQLA. Just my $0.02, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "SQLElixir" group. To post to this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sqlelixir?hl=.
