-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Max in main #61
Max in main #61
Conversation
The reason is that we want those to be inline in the table, we don't want to have to fetch them via toast. It's the large records array we want toasted
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, some of the tables are now being automatically generated (there are so many datasources now), so you need to also change powa_generic_module_setup()
, see https://github.com/powa-team/powa-archivist/blob/v5/powa--5.0.0dev.sql#L1356-L1357
And yes I agree that this function is really unreadable, but it still defeats copy/pasting dozen of times what's being generated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Thanks a lot, merged! |
All mins_in_range and maxs_in_range should be storage main. The reason is that we want those to be inline in the table, we don't want to have to fetch them via toast. It's the large records array we want toasted.
All mins_in_range and maxs_in_range should be storage main. The reason is that we want those to be inline in the table, we don't want to have to fetch them via toast. It's the large records array we want toasted.
All mins_in_range and maxs_in_range should be storage main. The reason is that we want those to be inline in the table, we don't want to have to fetch them via toast. It's the large records array we want toasted.
Close #60
All mins_in_range and maxs_in_range should be storage main
The reason is that we want those to be inline in the table, we don't
want to have to fetch them via toast. It's the large records array we
want toasted