On Dec 12, 2007, at 5:23 PM, Michael Bayer wrote:
> > > On Dec 12, 2007, at 4:49 PM, Adam Batkin wrote: > >> >> I would think it could be an option on the Table (err, Column) itself >> and not a mapper option. Something like pending_flush=True (which can >> default to False to keep the current behavior...though that name >> probably isn't very good, but flush_when_pending_on_read is too >> long ;). >> >> Does that sound like a reasonable idea? You don't have to commit to >> any >> work if you don't want, I wouldn't mind trying my hand at it if >> necessary. > > > Tables and Columns dont know anything about flushes, theyre external > to the ORM package. such a flag would be meaningless on a Column. how about just a flag on mapper (eager_pks=True) ? all the other mapper behavior is configured there so i think thats where it would be most consistent. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
