Thanks for the quick response, Michael.
We are mapping the classes dynamically, and we patched an in-house
copy of SQLAlchemy 0.5.6 with the stricter mutex from SQLAlchemy 0.6
to fix the sporadic mappers failed to compile errors we were seeing
under production load.
We also added a Least
diana wrote:
Case 3) In addition to the tables common across the N shards
(table_orange, table_yellow, etc), there are a bunch of tables that
have the same table definitions, yet different (but predictable) table
names. And by a bunch, I mean thousands of each table type per shard.
Attn Michael Bayer:
First off, thank-you so much for SQLAlchemy!
I've signed up for your two PyCon 2010 Atlanta tutorials, but I think
I'm going to need some guidance sooner rather than later (if
possible).
(database details below)
We've managed to make a legacy database mostly work with
