I put into the wiki's recipe section a working version of all this,
for those who are interested.
Incidentally -- I know the join's ambiguous, but while we're guessing
with cascade_mapper (that is, if it's going to be used as a feature),
we might as well guess intelligently. Does the current
im not a huge fan of cascade_mapper for reasons like this.
since you have an ambiguous join, perhaps youre looking for explicit
join conditions ?
http://www.sqlalchemy.org/docs/
adv_datamapping.myt#adv_datamapping_relations_customjoin
On Mar 26, 2006, at 1:05 PM, Gambit wrote:
Hi guys -
Hi guys -
I'm not sure this is a bug or not, but if not it might be worth
adding a comment to the documentation.
Using the following schema:
table A:
pk
B_fk_1
B_fk_2
...
table B:
pk
info
After setting up A and B correctly (see attachment), and
3 matches
Mail list logo
