dbrow seems to be exactly what ResultProxy already does (which has no speed problems).
the answer is in optimizing the "copy" made of each object's state upon load. step 1 is to make that an optional step, do some speed tests to insure that it speeds things up when disabled, step 2 is to possibly make that "copy" only take place when you actually modify the loaded object, so that the load operation is fast. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
