I have read about hibernate's shard strategy<http://www.hibernate.org/hib_docs/shards/reference/en/html/shards-shardstrategy.html> , and sqlalchemy's shard implementation. which remind me of a system in my company which implemented similar function, but both hibernate and sqlalchemy only separate data into multiple databases, but our system not only separate data into multiple databases but also into multiple tables of each database. i.e. there's not just db1,db2,db3... , but in each database, there is also table_weather_locations_1, table_weather_locations_2, table_weather_locations_3 ... I think the main reason for separating data into tables is when a table become huge the operations on that table would become slow. Then i'm wondering why both hibernate and sqlalchemy don't do that.
-- http://codeplayer.blogspot.com/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
