jordi fita mas
7f31b10cce
This is the same as a payment, but the user is the payee instead of the payer. I used a different relation than payment because i do not know any other way to encode the constraint that only invoices can have a collection, while expenses have only payments. Besides the name and the fact that they are related to invoices, a collection is pretty much the same as a payment.
33 lines
745 B
PL/PgSQL
33 lines
745 B
PL/PgSQL
-- Deploy numerus:invoice_collection to pg
|
|
-- requires: roles
|
|
-- requires: schema_numerus
|
|
-- requires: invoice
|
|
-- requires: collection
|
|
|
|
begin;
|
|
|
|
set search_path to numerus, public;
|
|
|
|
create table invoice_collection (
|
|
invoice_id integer not null references invoice,
|
|
collection_id integer not null references collection,
|
|
primary key (invoice_id, collection_id)
|
|
);
|
|
|
|
grant select, insert, update, delete on table invoice_collection to invoicer;
|
|
grant select, insert, update, delete on table invoice_collection to admin;
|
|
|
|
alter table invoice_collection enable row level security;
|
|
|
|
create policy company_policy
|
|
on invoice_collection
|
|
using (
|
|
exists(
|
|
select 1
|
|
from invoice
|
|
where invoice.invoice_id = invoice_collection.invoice_id
|
|
)
|
|
);
|
|
|
|
commit;
|