[sqlalchemy] Re: relation with same class/table on both sides

2008-07-09 Thread Tom Hogarty
The manager and direct reports example was just what my project needed. I'm looking forward to upgrading to 0.5 in the future so that I don't have to enter redundant primaryjoin and secondaryjoin on the backref. Thank you Mike! On Jun 28, 1:10 am, Tom Hogarty [EMAIL PROTECTED] wrote: Wow

[sqlalchemy] do not load large binary column but make available on demand

2008-07-09 Thread Tom Hogarty
Hello, I have a table that stores binary file data in one column and information about the file (file name, mime type, sha1 sum, etc) in the other columns. Currently when I use the mapped class, it loads the file data (adds to network and memory load). What I would like to do is check the sha1

[sqlalchemy] Re: do not load large binary column but make available on demand

2008-07-09 Thread Tom Hogarty
Deferred column loading is exactly what I needed, thanks Rick! Coming from a pure SQL background I'm starting to get familiar with all this new ORM and SQLAlchemy terminology. It's worth it though, the code is so much cleaner and more maintainable than stringing together huge complicated SQL

[sqlalchemy] relation with same class/table on both sides

2008-06-27 Thread Tom Hogarty
Hello, I have the following scenario where I want the same class/table on both sides of a relation. person table - id - name manager table - person_id - manager_id I define both tables and a Person class, then create a relation in the person mapper like: 'manager' : relation(Person,

[sqlalchemy] Re: relation with same class/table on both sides

2008-06-27 Thread Tom Hogarty
an error without them).  an   example is attached.  test.py 1KDownload On Jun 27, 2008, at 5:30 PM, Tom Hogarty wrote: Hello, I have the following scenario where I want the same class/table on both sides of a relation. person table - id - name manager table - person_id

[sqlalchemy] Re: allow_column_override

2008-06-17 Thread Tom Hogarty
Thanks for the info, I had the same problem and was able to fix it by renaming my relation to not override the other one and turning off allow_override. Removing allow_column_override would help eliminate the confusion since replacing the column makes the relation not work without the