was filter_by added recently? I have a assign_mapped class User from
TG, and doing a session.query(User).filter_by doesn't work (no such
method).
On 4/4/07, Michael Bayer [EMAIL PROTECTED] wrote:
My preference with assign_mapper at this point is to say:
Client.query.filter_by(sites=siteobj)
Ram Yalamanchili ha scritto:
was filter_by added recently? I have a assign_mapped class User from
TG, and doing a session.query(User).filter_by doesn't work (no such
method).
yes, it's in the latest 0.3.6 version...
this sometime it's hopeful :-)
- orm:
- the full featureset of
Glauco ha scritto:
Ram Yalamanchili ha scritto:
was filter_by added recently? I have a assign_mapped class User from
TG, and doing a session.query(User).filter_by doesn't work (no such
method).
yes, it's in the latest 0.3.6 version...
this sometime it's hopeful :-)
Michael Bayer wrote:
My preference with assign_mapper at this point is to say:
Client.query.filter_by(sites=siteobj)
For the mailing list's archives correctness:
Client.query().filter_by(sites=siteobj)
i.e. i dont think constantly adding methods to assignmapper is going
to scale,
Okay, thanks. Any idea if .filter_by() and other new generative method
will be available in an assign_mapper object?
http://www.sqlalchemy.org/docs/plugins.html#plugins_assignmapper
I'm figuring out that join_via and join_to will no longer be used as
it's not documented anymore and will be
Alexandre CONRAD ha scritto:
Okay, thanks. Any idea if .filter_by() and other new generative method
will be available in an assign_mapper object?
Yes..it's available, the final object has identical property as a mapper
Glauco
--
Glauco wrote:
Alexandre CONRAD ha scritto:
Okay, thanks. Any idea if .filter_by() and other new generative method
will be available in an assign_mapper object?
Yes..it's available, the final object has identical property as a mapper
Well, model.Client.filter_by(sites=siteobj) doesn't
My preference with assign_mapper at this point is to say:
Client.query.filter_by(sites=siteobj)
i.e. i dont think constantly adding methods to assignmapper is going
to scale, as the chances of conflicts with existing user classes
grows. im into hierarchies of names rather than huge
On Apr 3, 12:39 pm, Alexandre CONRAD [EMAIL PROTECTED] wrote:
And I'd like to find all attachments from one client. But as there's a
weak (secondary) table in between, I can no longer have something like:
model.Attachment.id_client==c.client.id
How can I achieve this ?
using a
