Hi Conor and rest of the list...
Well... I'm afraid I need to keep it separated. In the real model each
child is a list that is accessed in different ways (and do different
things) depending on which child it is.
I was wondering what it would be better (more correct) from a
relational point of
Hello list...
I wrote a couple of days ago about how to model an structure of three
classes
(http://groups.google.com/group/sqlalchemy/browse_thread/thread/5ba5c4ad16f789d6#).
I thing I almost have it, but I am still getting problems mapping an
structure like this.
class Child(rdb.Model):
On 10/29/2010 09:43 AM, Hector Blanco wrote:
Hello list...
I wrote a couple of days ago about how to model an structure of three
classes
(http://groups.google.com/group/sqlalchemy/browse_thread/thread/5ba5c4ad16f789d6#).
I thing I almost have it, but I am still getting problems mapping an
Thanks Conor!
The callable works like a charm! It's great news! (I've been trying to
figure out this for 3 days... yeah... I guess I'm not that smart)
Now that I have it working, a “design” question pops up. Nothing
technical, really.
As Connor mentioned in his reply:
“Usually we consider the
On 10/29/2010 11:51 AM, Hector Blanco wrote:
Thanks Conor!
The callable works like a charm! It's great news! (I've been trying to
figure out this for 3 days... yeah... I guess I'm not that smart)
Now that I have it working, a “design” question pops up. Nothing
technical, really.
As Connor
