On Wednesday, January 20, 2016 at 7:05:35 PM UTC-5, Amy Smith wrote: > > I put "sharded" in quotes because it is almost certainly not the correct > technical term for what I'm trying to do. >
That strategy is commonly called "partitioning", and more specifically "table partitioning". Depending on your database backend, it may be (largely) transparently handled with master/child relationships. Here's some non-sqlalchemy info on postgres (docs + example) http://www.postgresql.org/docs/9.5/static/ddl-partitioning.html https://blog.engineyard.com/2013/scaling-postgresql-performance-table-partitioning There are some recipes and examples on the sqlalchemy.org site for implementing postgres's partitioning. There's probably a bunch more info in the messages archives under "partitioned" though. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
