Robin Munn wrote:
Seems to me like it would be nice, too. The one concern I have is whether there are any attributes of ResultProxy or RowProxy that could get shadowed by column names. Since there's an alternate way of specifying columns, via __getitem__, I think in cases of shadowing, the Result/RowProxy attribute should trump the column name.
I've just committed the change, but thinking about this I wonder if we should flag an error if there is a clash between the RowProxy's 'parent' and 'row' attributes and any column names to avoid any element of surprise. Maybe a rename to _parent and _row or similar, along with an error in the unlikely event that a clash occurs? Thoughts?
Robert ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Sqlalchemy-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
