2👍
-
In the vast majority of cases, this shouldn’t buy you any performance advantage. Any RDBMS worth its salt should handle immense tables effortlessly.
-
If it’s needed, there could be some sharding of the table. Again, managed by the DB server; at SQL level (and ORM) it should be seen as a single table. Ideally, the discrimination should be automatically handled; if not, most RDBMS let you specify it at table definition time (or sometimes tune with ALTER TABLE)
-
If you choose to define the sharding method, each RDBMS has it’s own non-standard methods. Best not to tie your Python code to that; do the tuning once on the DB server instead.
Source:stackexchange.com