[sqlalchemy] Re: join_depth in two directions with adjancency lists

2008-12-26 Thread Wichert Akkerman
On 12/25/08 4:37 PM, Michael Bayer wrote: On Dec 25, 2008, at 6:45 AM, Wichert Akkerman wrote: I have a reasonably standard hierarchical datastructure which I'm trying to store in SQL. The basic model looks like this: class Page(BaseObject): __tablename__ = page id =

[sqlalchemy] Re: join_depth in two directions with adjancency lists

2008-12-26 Thread Michael Bayer
On Dec 26, 2008, at 5:08 AM, Wichert Akkerman wrote: It did not though: I only got the direct parent. if you could save me some time and post a full example that I can run that would be helpful. To roll those up into a single set of result columns in a single SQL statement would be

[sqlalchemy] Re: using key parameter at column definition

2008-12-26 Thread Michael Bayer
you should use lower case names for the columns if they are case insensitive names. Check the API reference with regards to the Column() constructor for details on this. Also ForeignKey() by default should reference the given key on the Column, not the name. I see you have used the key

[sqlalchemy] Updating existing objects

2008-12-26 Thread Eric Abrahamsen
Sorry for the very beginner question, but I haven't been able to find a good discussion of this issue online (possibly because it's too basic). I'm using sqlalchemy as part of a basic web-based CRUD-style CMS. I've got the Create, Read and Delete parts down, but I'm not sure how best to handle

[sqlalchemy] Re: Updating existing objects

2008-12-26 Thread Andreas Jung
On 27.12.2008 3:06 Uhr, Eric Abrahamsen wrote: Sorry for the very beginner question, but I haven't been able to find a good discussion of this issue online (possibly because it's too basic). I'm using sqlalchemy as part of a basic web-based CRUD-style CMS. I've got the Create, Read and