Replies: 2 comments 3 replies
-
a) I wouldn't list the partitions by default (a plugin can change it with Adding the support for declarative partitioning doesn't seem too complicated to me. |
Beta Was this translation helpful? Give feedback.
2 replies
-
BTW how do you create partitions for new data? With a cronjob or is there something higher level? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
By accident, I have found out that MySQL has better support for Partitioning than PostgreSQL; that's something I can't tolerate! :)
I'm willing to create a PR, but there are some design decisions that must be addressed
How to list partitions in a list of tables?

a) Should the partitions be listed at all? I think so..
b) Should it be somehow distinguished? I think that giving it some prefix "P: TableName" for example will be great. There should also be a tooltip on the top of the "P:" which will show the name of the parent table
In detail of a given table, we can be probably more verbose so using something like a breadcrumb
Parent Table -> Current Table with a link to a parent might be handy
I would propose splitting the partitioning support to two levels... "partitioning_view" | "partitioning_edit"
Partitioning is quite a complex feature, and TBH, I don't think that edit support is really necessary. I would aim (at least at the beginning) to only show the necessary information. At the table detail page (list of partitions), but without the possibility to edit it. I guess it would be more complicated and the benefit of it will be negligible.
Ideas / Opinions?
Beta Was this translation helpful? Give feedback.
All reactions