I would second that, I wouldn't go with Elixir now at all, given the continuing maturity of sqlalchemy. Ahmed
On Jan 4, 10:27 am, Siddhartha Kasivajhula <countvajh...@gmail.com> wrote: > Thanks for the detailed explanation Mike! SQLAHelper sounds really handy. > Re: Elixir, I only took a brief look around and I'm not yet about to build > anything, but from this initial evaluation it seems like Sqlalchemy's ORM > is still pretty lowlevel/sql-heavy -- like the use of the words "Column" > and "Table" at the ORM layer is to me the wrong level of abstraction I'd > like there. It doesn't look all that Elixir-inspired to my untrained eye, > but as Michael pointed out there hasn't been a release of Elixir since > 2009, so I guess SQLAlchemy / declarative is the way to go... > > -Sid > > > > > > > > > > On Tue, Jan 3, 2012 at 12:25 PM, Mike Orr <sluggos...@gmail.com> wrote: > > On Tue, Jan 3, 2012 at 11:49 AM, Siddhartha Kasivajhula > > <countvajh...@gmail.com> wrote: > > > Sorry if this is a bit off-topic, but does Elixir > > > (http://elixir.ematia.de/trac/wiki) fit in anywhere in this discussion? > > I'm > > > a relative newcomer to pyramid and I've been meaning to use Elixir on > > top of > > > SQLAlchemy when I do write a SQL-based app (so far my only experience > > with > > > pyramid has been simple apps that didn't need a SQL layer). Seems like > > > SQLAHelper may be for more nuanced use cases but just thought I'd ask for > > > clarification while this email thread is active. > > > Elixir and SQLAHelper address different questions. SQLAlchemy by > > itself has an API to define tables and ORM classes. SQLAHelper is a > > container to organize one's engines, sessions, and declarative bases > > -- it does not deal directly with ORM classes. Elixir provides a > > "super-declarative" syntax for defining ORM classes, and may provide > > additional "active record" features beyond that. > > > Elixir was released at a time before SQLAlchemy's declarative syntax > > existed. MikeB added declarative after many long clamors for this > > feature, but he did it in a minimal way, to offer just enough syntax > > sugar without getting too magical. Elixir may go beyond that but I'm > > not sure. So I don't know whether Elixir has any added value now that > > declarative is in standard SQLAlchemy. > > > In any case, there's two different issues: "Can I use Elixir with > > Pyramid?" and "Will Pyramid officially support Elixir, or include it > > as a default feature?" The answer to the first question is, "Probably. > > You can ask about Elixir on this list or look in the Pyramid Cookbook > > for user-contributed articles on it." The answer to the second > > question is, "No, it's a high-level library, and Pyramid includes only > > medium-level libraries. E.g., there's built-in support for SQLAlchemy, > > but not for any particular form library." > > > SQLAHelper is kind of between official and unofficial support. Whether > > it should be an official default or not, is what people in this thread > > have been discussing. > > > -- > > Mike Orr <sluggos...@gmail.com> > > On Tue, Jan 3, 2012 at 12:23 PM, Siddhartha Kasivajhula < > > > > > > > > countvajh...@gmail.com> wrote: > > Don't hijack threads, this is an active mailing list and other threads > >> will receive answers as well. > >> Elixir has not seen a release since 2009 and is largely the inspiration > >> for SQLAlchemy's current declarative syntax which should be used in new > >> projects. > > > My bad, I did consider starting another thread but ended up deciding the > > question was relevant for this one. Thanks for the info! > > > On Tue, Jan 3, 2012 at 12:13 PM, Michael Merickel <mmeri...@gmail.com> > > wrote: > > >> On Tue, Jan 3, 2012 at 1:49 PM, Siddhartha Kasivajhula < > >> countvajh...@gmail.com> wrote: > > >>> Sorry if this is a bit off-topic, but does Elixir ( > >>>http://elixir.ematia.de/trac/wiki) fit in anywhere in this discussion? > >>> I'm a relative newcomer to pyramid and I've been meaning to use Elixir on > >>> top of SQLAlchemy when I do write a SQL-based app (so far my only > >>> experience with pyramid has been simple apps that didn't need a SQL > >>> layer). > >>> Seems like SQLAHelper may be for more nuanced use cases but just thought > >>> I'd ask for clarification while this email thread is active. Thanks :) > > >>> -Sid > > >> Don't hijack threads, this is an active mailing list and other threads > >> will receive answers as well. > >> Elixir has not seen a release since 2009 and is largely the inspiration > >> for SQLAlchemy's current declarative syntax which should be used in new > >> projects. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
