numerus/verify/contact_tag.sql

-- Verify numerus:contact_tag on pg

begin;

select contact_id
     , tag_id
from numerus.contact_tag
where false;

select 1 / count(*) from pg_class where oid = 'numerus.contact_tag'::regclass and relrowsecurity;
select 1 / count(*) from pg_policy where polname = 'company_policy' and polrelid = 'numerus.contact_tag'::regclass;

rollback;
Add tags for contacts too With Oriol we agreed that contacts should have tags, too, and that the “tag pool”, as it were, should be shared with the one for invoices (and all future tags we might add). I added the contact_tag relation and tag_contact function, just like with invoices, and then realized that the SQL queries that Go had to execute were becoming “complex” enough: i had to get not only the slug, but the contact id to call tag_contact, and all inside a transaction. Therefore, i opted to create the add_contact and edit_contact functions, that mirror those for invoice and products, so now each “major” section has these functions. They also simplified a bit the handling of the VATIN and phone numbers, because it is now encapsuled inside the PL/pgSQL function and Go does not know how to assemble the parts. 2023-03-26 00:32:53 +00:00			`-- Verify numerus:contact_tag on pg`

			`begin;`

			`select contact_id`
			`, tag_id`
			`from numerus.contact_tag`
			`where false;`

			`select 1 / count(*) from pg_class where oid = 'numerus.contact_tag'::regclass and relrowsecurity;`
			`select 1 / count(*) from pg_policy where polname = 'company_policy' and polrelid = 'numerus.contact_tag'::regclass;`

			`rollback;`