jordi fita mas
b4919db6c4
Seasons have a color to show on the calendar. I need them in HTML format (e.g., #123abc) in order to set as value to `<input type="color">`, but i did not want to save them as text in the database, as integers are better representations of colors—in fact, that’s what the HTML syntax also is: an integer. I think the best would be to create an extension that adds an HTML color type, with functions to convert from many representations (e.g., CSS’ rgb or even color names) to integer and back. However, that’s a lot of work and i can satisfy Camper’s needs with just a couple of functions and a domain. To show the color on the index, at first tried to use a read-only `<input type="color">`, but seems that this type of input can not be read-only and must be disabled instead. However, i do not know whether it makes sense to have a disabled input outside a form “just” to show a color; i suspect it does not. Thus, at the end i use SVG with a single circle, which is better that a 50%-rounded div with a background color, even if the result is the same—SVG **is** intended for showing pictures, which is this case.
28 lines
653 B
PL/PgSQL
28 lines
653 B
PL/PgSQL
-- Deploy camper:edit_season to pg
|
|
-- requires: roles
|
|
-- requires: schema_camper
|
|
-- requires: season
|
|
-- requires: color
|
|
-- requires: to_integer
|
|
|
|
begin;
|
|
|
|
set search_path to camper, public;
|
|
|
|
create or replace function edit_season(slug uuid, name text, color color, active boolean) returns uuid as $$
|
|
update season
|
|
set name = edit_season.name
|
|
, color = to_integer(edit_season.color)
|
|
, active = edit_season.active
|
|
where slug = edit_season.slug
|
|
returning slug
|
|
;
|
|
$$
|
|
language sql
|
|
;
|
|
|
|
revoke execute on function edit_season(uuid, text, color, boolean) from public;
|
|
grant execute on function edit_season(uuid, text, color, boolean) to admin;
|
|
|
|
commit;
|