Thanks Michael, I am
trying to build up the complexity one piece at a time, and you've already
answered several issues up to this point. Like you said in the earlier email,
this is an atypical mapping and I'm impressed to date with how well SA has been
handling it. I'll try to find ways of m
actually, heres both tests passing. however, i am sure this mapping is going to have more problems, its really complicated. one for the test suite for sure if it ever works fully.from sqlalchemy import *
import time
import os
metadata = DynamicMetaData()
tables = {}
class Project(object):
d
youve got relationships defined on your mappers which are essentially "view only". particularly when you specify a primaryjoin that crosses two tables, the unit of work cant do anything with that. if you look at the flush plan (using create_session(echo_uow=True)), youll see that in the first tes
3 matches
Mail list logo
