On Aug 19, 2010, at 10:39 PM, Eduardo Robles Elvira wrote:
Hello everyone:
This is my first post in this mailing list/group. My question is
simple: is there some way to tell sqlalchemy which method should be
called to instance models? Now, some background:
I'm working in a project with
-Original Message-
From: sqlalchemy@googlegroups.com
[mailto:sqlalch...@googlegroups.com] On Behalf Of Michael Hipp
Sent: 19 August 2010 23:39
To: sqlalchemy@googlegroups.com
Subject: Re: [sqlalchemy] Which columns changing during orm commit?
On 8/19/2010 5:24 AM, Chris Withers
On Fri, Aug 20, 2010 at 7:39 AM, Eduardo Robles Elvira edu...@gmail.comwrote:
Now, these functions reimplemented in the inherited class models might
be called by the jobs view. It would be very convenient if directly
when I get the jobs from the database with sqlalchemy I could directly
get
On Fri, Aug 20, 2010 at 10:34 AM, Daniel Kluev dan.kl...@gmail.com wrote:
On Fri, Aug 20, 2010 at 7:39 AM, Eduardo Robles Elvira edu...@gmail.com
wrote:
Now, these functions reimplemented in the inherited class models might
be called by the jobs view. It would be very convenient if directly
I've run into this a variant of this same problem several times now,
so I want to ask if you know of a good way to solve the problem.
Some relation()s are based on extra criteria (besides primary key
joins), but otherwise would be nice to work just like normal relation
properties.
A simplified
Now, thank you for the quick reply.
I might not be understanding what you need here, but assuming you want
your API to look like this:
product.sales('2010-08-20')
[Sale,Sale, ...]
Right, that is the idea.
First of all, is that enough? If you just want to dynamically access
an
