You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by theelderbeever May 24, 2022
Background on the question... some of our tables are very large and our deployment infrastructure limits us to 16TB of disk space per provisioned drive. Having all of the tables on the same drive runs the risk of filling up our drive. We would like to set tables to tablespaces so we can provision drives on a per table/tablespace basis.
Is there a way to CREATE TABLE foo(i int) TABLESPACE space1; when generating the ORM Models?
Is the solution to generate empty tables using a raw SQL migration and then add the models in the next migration? Would Piccolo perform the correct ALTER TABLE commands if the tables weren't generated via the ORM models?
The text was updated successfully, but these errors were encountered:
Discussed in #525
Originally posted by theelderbeever May 24, 2022
Background on the question... some of our tables are very large and our deployment infrastructure limits us to 16TB of disk space per provisioned drive. Having all of the tables on the same drive runs the risk of filling up our drive. We would like to set tables to tablespaces so we can provision drives on a per table/tablespace basis.
Is there a way to
CREATE TABLE foo(i int) TABLESPACE space1;
when generating the ORM Models?Is the solution to generate empty tables using a raw SQL migration and then add the models in the next migration? Would Piccolo perform the correct
ALTER TABLE
commands if the tables weren't generated via the ORM models?The text was updated successfully, but these errors were encountered: