any chance we can see an example of what kind of usage youre looking for ? i thought we just were talking about adding an "order by" property to an ActiveMapper relation (which is pretty trivial) ?
Charles Duffy wrote: > This is considerably more interesting than I expected. > > So -- one already needs to process deferrals based on relations. What's > needed to support arbitrary keyword arguments (many of which will refer > to other tables and their columns) is a reference type which also > triggers deferrals and can be found even if nested as a parameter to an > argument to a relation (or a list member in a parameter to an argument > to a relation!), or if mentioned somewhere inside __mapper_args__ (a new > mapping entry I'm creating for holding extra arbitrary arguments). > During processing, the reference objects are all looked up and replaced > with actual table/column references. > > Before I go and implement the deep-search-and-replace code to do it this > way, does anyone see a better approach? > > > > _______________________________________________ > Sqlalchemy-users mailing list > Sqlalchemy-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users > _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
