tandem
/
numerus
2
0
Fork 0
Code Issues 45 Pull Requests Packages Projects 1 Releases 1 Wiki Activity
numerus/deploy/remove_collection.sql

41 lines
1002 B
MySQL
Raw Normal View History

Add payment collection 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.
2024-08-21 01:36:12 +00:00
-- Deploy numerus:remove_collection to pg
-- requires: roles
-- requires: schema_numerus
Subsume collections into payments, and record payments in negative This is to handle refunds, which are invoices with negative amounts, that can be both issued or received (i.e., an “expense”). The API provided by PostgreSQL is mostly the same, and internally it deals with negatives, so the Go package only had to change selects of collection.
2025-01-30 22:24:16 +00:00
-- requires: invoice_payment
-- requires: payment
-- requires: payment_attachment
Add payment collection 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.
2024-08-21 01:36:12 +00:00
-- requires: update_invoice_collection_status
begin;
set search_path to numerus, public;
create or replace function remove_collection(collection_slug uuid) returns void as
$$
declare
cid integer;
iid integer;
begin
Subsume collections into payments, and record payments in negative This is to handle refunds, which are invoices with negative amounts, that can be both issued or received (i.e., an “expense”). The API provided by PostgreSQL is mostly the same, and internally it deals with negatives, so the Go package only had to change selects of collection.
2025-01-30 22:24:16 +00:00
select payment_id into cid from payment where slug = collection_slug;
Add payment collection 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.
2024-08-21 01:36:12 +00:00
if not found then
return;
end if;
Subsume collections into payments, and record payments in negative This is to handle refunds, which are invoices with negative amounts, that can be both issued or received (i.e., an “expense”). The API provided by PostgreSQL is mostly the same, and internally it deals with negatives, so the Go package only had to change selects of collection.
2025-01-30 22:24:16 +00:00
delete from invoice_payment where payment_id = cid returning invoice_id into iid;
Add payment collection 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.
2024-08-21 01:36:12 +00:00
if iid is not null then
perform update_invoice_collection_status(null, iid, 0);
end if;
Subsume collections into payments, and record payments in negative This is to handle refunds, which are invoices with negative amounts, that can be both issued or received (i.e., an “expense”). The API provided by PostgreSQL is mostly the same, and internally it deals with negatives, so the Go package only had to change selects of collection.
2025-01-30 22:24:16 +00:00
delete from payment_attachment where payment_id = cid;
delete from payment where payment_id = cid;
Add payment collection 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.
2024-08-21 01:36:12 +00:00
end
$$
language plpgsql
;
revoke execute on function remove_collection(uuid) from public;
grant execute on function remove_collection(uuid) to invoicer;
grant execute on function remove_collection(uuid) to admin;
commit;