I'd agree that elixir is fine for large scale projects (we are using it from the early days on), but indeed, make sure to get some sqlalchemy knowledge, just to know when you have to switch to plain sqlalchemy.
Also sqlalchemy-migrate is something you better have a look at... Good luck ! On Jul 25, 7:27 pm, yoav glazner <[email protected]> wrote: > On Sun, Jul 25, 2010 at 6:51 PM, Michael Hipp <[email protected]> wrote: > > Hello, > > > 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 > > Hi Michael, > > I started working with elixir about a year ago without any SA knowlage and > got burned a few times because of SA related issues, > If you already know SA this won't be an issue for you. > Anyway, each issue was resolved since elixir doesn't impose constraints that > are not already in SA. > > thats my 10 cents, > > G'day, > > Yoav Glazner -- 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.
