Make home page’s carousel manageable via the database
I debated with myself whether to create the home_carousel relation or
rather if it would be better to have a single carousel relation for all
pages. However, i thought that it would be actually harder to maintain
a single relation because i would need an additional column to tell one
carrousel from another, and what would that column be? An enum? A
foreign key to another relation? home_carousel carries no such issues.
I was starting to duplicate logic all over the packages, such as the
way to encode media paths or “localization” (l10n) input fields.
Therefore, i refactorized them.
In the case of media path, i added a function that accepts rows of
media, because always need the same columns from the row, and it was
yet another repetition if i needed to pass them all the time. Plus,
these kind of functions can be called as `table.function`, that make
them look like columns from the table; if PostgreSQL implemented virtual
generated columns, i would have used that instead.
I am not sure whether that media_path function can be immutable. An
immutable function is “guaranteed to return the same results given the
same arguments forever”, which would be true if the inputs where the
hash and the original_filename columns, instead of the whole rows, but
i left it as static because i did not know whether PostgreSQL interprets
the “same row but with different values” as a different input. That is,
whether PostgreSQL’s concept of row is the actual tuple or the space
that has a rowid, irrespective of contents; in the latter case, the
function can not be immutable. Just to be in the safe side, i left it
stable.
The home page was starting to grow a bit too much inside the app
package, new that it has its own admin handler, and moved it all to a
separate package.
2023-09-14 23:05:38 +00:00
|
|
|
-- Deploy camper:home_carousel to pg
|
|
|
|
|
-- requires: roles
|
2023-10-12 14:21:32 +00:00
|
|
|
-- requires: schema_camper
|
Make home page’s carousel manageable via the database
I debated with myself whether to create the home_carousel relation or
rather if it would be better to have a single carousel relation for all
pages. However, i thought that it would be actually harder to maintain
a single relation because i would need an additional column to tell one
carrousel from another, and what would that column be? An enum? A
foreign key to another relation? home_carousel carries no such issues.
I was starting to duplicate logic all over the packages, such as the
way to encode media paths or “localization” (l10n) input fields.
Therefore, i refactorized them.
In the case of media path, i added a function that accepts rows of
media, because always need the same columns from the row, and it was
yet another repetition if i needed to pass them all the time. Plus,
these kind of functions can be called as `table.function`, that make
them look like columns from the table; if PostgreSQL implemented virtual
generated columns, i would have used that instead.
I am not sure whether that media_path function can be immutable. An
immutable function is “guaranteed to return the same results given the
same arguments forever”, which would be true if the inputs where the
hash and the original_filename columns, instead of the whole rows, but
i left it as static because i did not know whether PostgreSQL interprets
the “same row but with different values” as a different input. That is,
whether PostgreSQL’s concept of row is the actual tuple or the space
that has a rowid, irrespective of contents; in the latter case, the
function can not be immutable. Just to be in the safe side, i left it
stable.
The home page was starting to grow a bit too much inside the app
package, new that it has its own admin handler, and moved it all to a
separate package.
2023-09-14 23:05:38 +00:00
|
|
|
-- requires: company
|
|
|
|
|
-- requires: media
|
|
|
|
|
-- requires: user_profile
|
|
|
|
|
|
|
|
|
|
begin;
|
|
|
|
|
|
|
|
|
|
set search_path to camper, public;
|
|
|
|
|
|
|
|
|
|
create table home_carousel (
|
|
|
|
|
media_id integer not null references media primary key,
|
|
|
|
|
caption text not null
|
|
|
|
|
);
|
|
|
|
|
|
|
|
|
|
grant select on table home_carousel to guest;
|
|
|
|
|
grant select on table home_carousel to employee;
|
|
|
|
|
grant select, insert, update, delete on table home_carousel to admin;
|
|
|
|
|
|
|
|
|
|
alter table home_carousel enable row level security;
|
|
|
|
|
|
|
|
|
|
create policy guest_ok
|
|
|
|
|
on home_carousel
|
|
|
|
|
for select
|
|
|
|
|
using (true)
|
|
|
|
|
;
|
|
|
|
|
|
|
|
|
|
create policy insert_to_company
|
|
|
|
|
on home_carousel
|
|
|
|
|
for insert
|
|
|
|
|
with check (
|
|
|
|
|
exists (select 1 from media join user_profile using (company_id) where media.media_id = home_carousel.media_id)
|
|
|
|
|
)
|
|
|
|
|
;
|
|
|
|
|
|
|
|
|
|
create policy update_company
|
|
|
|
|
on home_carousel
|
|
|
|
|
for update
|
|
|
|
|
using (
|
|
|
|
|
exists (select 1 from media join user_profile using (company_id) where media.media_id = home_carousel.media_id)
|
|
|
|
|
)
|
|
|
|
|
;
|
|
|
|
|
|
|
|
|
|
create policy delete_from_company
|
|
|
|
|
on home_carousel
|
|
|
|
|
for delete
|
|
|
|
|
using (
|
|
|
|
|
exists (select 1 from media join user_profile using (company_id) where media.media_id = home_carousel.media_id)
|
|
|
|
|
)
|
|
|
|
|
;
|
|
|
|
|
|
|
|
|
|
commit;
|