Have you considered using a discriminator column, an additional integer that identifies the shard and is part of a two-integer primary key?
You could then use concrete polymorphic inheritance to set up mappers for both tables that would automatically set the discriminator column to the appropriate shard id for saves. I'm not familiar with the current shard support in SQLA, but it may already provide something along these lines.... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
