Both
session.query(User).select()
and
User.query().select()
seem more verbose than they need to be for my taste. However, I think most
people (myself included) define a base class for all their mapped classes.
I've always used this base class to provide the interface I want, no matter
what interface sqlalchemy provides (and SA's API has changed quite a bit
since 0.1). I suppose if anyone is going to pollute the namespace of the
User class, it should be me, not sqlalchemy.
That said, if I was new to sqlalchemy, I think I'd be scared to see
session.query(User).select() as the "recommended way" in the tutorial.
So, +1/2 from me on ditching assign_mapper (while keeping SessionContext, of
course).
shoe
On 6/1/07, Michael Bayer <[EMAIL PROTECTED]> wrote:
>
>
>
> On Jun 1, 2007, at 12:46 PM, Gaetan de Menten wrote:
>
> > To get this straight, this was my personal opinion, not the one from
> > the whole "elixir crew". The other option which was discussed was to
> > get rid of assignmapper altogether (in favor of defining the methods
> > on our base class so that people can override those in their own
> > classes ). No final decision was taken on this issue yet.
> > --
>
> I like that latter idea too. assignmapper was a hack from day one.
> good job elixir crew ! ;)
>
>
>
> >
>
--
--- I'd give my right arm to be ambidextrous. ---
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
