Thanks, Michael. This will take me a bit to digest, and I'm about to start the second shift as wife and mother... tomorrow maybe.
Thanks again for the quick responses -- greatly exceeding expectations! Cheers, --diana On Mon, Jan 11, 2010 at 5:14 PM, Michael Bayer <mike...@zzzcomputing.com> wrote: > well there's two things, one left over from previous. one is that > commit() expires all attributes in the session. that is why new SQL is > emitted. check the docs for rationale there. > > but also, the loading of deferred attributes as earlier and expired > attributes here does have the primary key, so its a bug that shard_chooser > is being run here, since the internal function doing that is calling > query._get(), whereas ShardedQuery is being simple and only overriding > get(). You might want to change ShardedQuery to override _get() instead > (which leads me further towards pulling the trigger of moving shard.py out > to examples altogether for 06, since it really is not supportable as a > core element, just FYI). > > Its also possibly worth it to get your ShardChooser to the point where it > can recognize what is effectively a get() based on filtering criterion. > You can do this by imitating the approach in the example FindContinent > chooser in examples/sharding/attribute_shard.py. > >> >> Thanks, >> >> --diana
-- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
