--- On Sun, 7/25/10, Michael Hipp <[email protected]> wrote: > I'm embarking on a sizable project and need to make some > decisions early on. Question... > > Is there any downside to using Elixir vs. straight > SQLAlchemy? > > I sure look like the look of Elixir's model definitions vs. > having to write everything twice in SA. > > Just hoped someone might be brutally honest if there's > something I might regret if I use Elixir. > > Thanks, > Michael Hipp >
Hello, I have used elixir on an early web application with no regrets, and I'm using it now for a desktop application. I had one major problem since then with foreign key constraints (see : http://groups.google.com/group/sqlelixir/browse_thread/thread/d7bcb1723f85dc13/97cff1dfc2de5f7a?lnk=gst&q=foreign+key+constraints+not+fired#97cff1dfc2de5f7a). Defining fk constraints in sqlalchemy is straight and meaningful. In elixir, I found it rather hard to understand. An ondelete="RESTRICT" should have been enough but it was not the case. Additionally, the solution to that problem was to use a passive_deletes = All, which was none trivial for me to understand. Anyway, I think elixir is a nice piece of code, and provides you with additional useful introspection tools that are embedded in your entities (like entity._mapper and entity._mapper.get_property). Cheers, Y.Chaouche. -- 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.
