Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Add support for tablespaces #526

Open
dantownsend opened this issue May 24, 2022 Discussed in #525 · 0 comments · May be fixed by #527
Open

Add support for tablespaces #526

dantownsend opened this issue May 24, 2022 Discussed in #525 · 0 comments · May be fixed by #527
Labels
enhancement New feature or request

Comments

@dantownsend
Copy link
Member

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?

@dantownsend dantownsend added the enhancement New feature or request label May 24, 2022
@dantownsend dantownsend linked a pull request May 24, 2022 that will close this issue
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant