Re: [Sqlalchemy-users] Many to Many mapping and inheritance

2006-02-26 Thread Michael Bayer
fyi i have made some commits today that should make the kind of many- to-many + inheritance thing youre doing work more smoothly...should you try it out please keep me apprised of how it goes. we're on a weekly to bi-weekly release schedule so you wont have to be on SVN for long. On Feb

Re: [Sqlalchemy-users] Many to Many mapping and inheritance

2006-02-26 Thread Michael Bayer
yup, youre totally going to be on SVN :) I see the pattern youre doing and I agree that is important. more support will be forthcoming :) - mike On Feb 26, 2006, at 11:53 AM, Florian Boesch wrote: Hm, I wonder, should I work with the svn version of sqlalchemy? Quoting Michael Bayer <[EM

Re: [Sqlalchemy-users] Many to Many mapping and inheritance

2006-02-26 Thread Florian Boesch
Hm, I wonder, should I work with the svn version of sqlalchemy? Quoting Michael Bayer <[EMAIL PROTECTED]>: > ok, i committed a very small change and applied several layers of > scotch tape to your example and it is roughly working. attached is a > test script which documents a few of the quirks

Re: [Sqlalchemy-users] Many to Many mapping and inheritance

2006-02-26 Thread Florian Boesch
The reason I do this "whacky" scheme is a simple content management system. Take this hirarchy for instance: content page linklist productlist product someproduct So I can identify each content item by a unique id, and content is also type tagged. Of course a linklist should refer

Re: [Sqlalchemy-users] Many to Many mapping and inheritance

2006-02-25 Thread Michael Bayer
ok, i committed a very small change and applied several layers of scotch tape to your example and it is roughly working. attached is a test script which documents a few of the quirks with this sort of thing right now. I have in mind some refactorings to make mapper inheritance a little st

Re: [Sqlalchemy-users] Many to Many mapping and inheritance

2006-02-25 Thread Michael Bayer
the issue here is that your inheritance and your related table are both to the same table, i.e. 'foo'. the logic that is breaking is where it tries to determine "which property must be synchronized between parent and child object, or between parent, child, and association table", since hon

[Sqlalchemy-users] Many to Many mapping and inheritance

2006-02-25 Thread Florian Boesch
I require that kind of thing, so I've assembled a little testcode to demonstrate the problems. Below is the vanilla many to many thing that doesn't error upon defintion (with one minor glitch at the mapper, see #comments) from sqlalchemy import * from sqlalchemy.ext.proxy import ProxyEngine engin