Skip to content
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

Merged
merged 3 commits into from
Apr 8, 2024
Merged

Max in main #61

merged 3 commits into from
Apr 8, 2024

Conversation

marco44
Copy link
Contributor

@marco44 marco44 commented Apr 8, 2024

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

@marco44 marco44 requested a review from rjuju April 8, 2024 12:55
@marco44 marco44 self-assigned this Apr 8, 2024
@marco44 marco44 changed the base branch from master to v5 April 8, 2024 12:58
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
Copy link
Member

@rjuju rjuju left a 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.

Copy link
Member

@rjuju rjuju left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@rjuju rjuju merged commit 2496f0b into v5 Apr 8, 2024
@rjuju
Copy link
Member

rjuju commented Apr 8, 2024

Thanks a lot, merged!

rjuju pushed a commit that referenced this pull request Apr 10, 2024
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.
rjuju pushed a commit that referenced this pull request Jun 15, 2024
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.
rjuju pushed a commit that referenced this pull request Jul 8, 2024
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

make the min/max fields stay in the main table
2 participants