2023-01-29 14:14:31 +00:00
|
|
|
-- Test contact
|
|
|
|
set client_min_messages to warning;
|
|
|
|
create extension if not exists pgtap;
|
|
|
|
reset client_min_messages;
|
|
|
|
|
|
|
|
begin;
|
|
|
|
|
Split contact relation into tax_details, phone, web, and email
We need to have contacts with just a name: we need to assign
freelancer’s quote as expense linked the government, but of course we
do not have a phone or email for that “contact”, much less a VATIN or
other tax details.
It is also interesting for other expenses-only contacts to not have to
input all tax details, as we may not need to invoice then, thus are
useless for us, but sometimes it might be interesting to have them,
“just in case”.
Of course, i did not want to make nullable any of the tax details
required to generate an invoice, otherwise we could allow illegal
invoices. Therefore, that data had to go in a different relation,
and invoice’s foreign key update to point to that relation, not just
customer, or we would again be able to create invalid invoices.
We replaced the contact’s trade name with just name, because we do not
need _three_ names for a contact, but we _do_ need two: the one we use
to refer to them and the business name for tax purposes.
The new contact_phone, contact_web, and contact_email relations could be
simply a nullable field, but i did not see the point, since there are
not that many instances where i need any of this data.
Now company.taxDetailsForm is no longer “the same as contactForm with
some extra fields”, because i have to add a check whether the user needs
to invoice the contact, to check that the required values are there.
I have an additional problem with the contact form when not using
JavaScript: i must set the required field to all tax details fields to
avoid the “(optional)” suffix, and because they _are_ required when
that checkbox is enabled, but i can not set them optional when the check
is unchecked. My solution for now is to ignore the form validation,
and later i will add some JavaScript that adds the validation again,
so it will work in all cases.
2023-06-30 19:32:48 +00:00
|
|
|
select plan(48);
|
2023-01-29 14:14:31 +00:00
|
|
|
|
|
|
|
set search_path to numerus, auth, public;
|
|
|
|
|
|
|
|
select has_table('contact');
|
|
|
|
select has_pk('contact' );
|
|
|
|
select table_privs_are('contact', 'guest', array []::text[]);
|
|
|
|
select table_privs_are('contact', 'invoicer', array ['SELECT', 'INSERT', 'UPDATE', 'DELETE']);
|
|
|
|
select table_privs_are('contact', 'admin', array ['SELECT', 'INSERT', 'UPDATE', 'DELETE']);
|
|
|
|
select table_privs_are('contact', 'authenticator', array []::text[]);
|
|
|
|
|
|
|
|
select has_sequence('contact_contact_id_seq');
|
|
|
|
select sequence_privs_are('contact_contact_id_seq', 'guest', array[]::text[]);
|
|
|
|
select sequence_privs_are('contact_contact_id_seq', 'invoicer', array['USAGE']);
|
|
|
|
select sequence_privs_are('contact_contact_id_seq', 'admin', array['USAGE']);
|
|
|
|
select sequence_privs_are('contact_contact_id_seq', 'authenticator', array[]::text[]);
|
|
|
|
|
|
|
|
select has_column('contact', 'contact_id');
|
|
|
|
select col_is_pk('contact', 'contact_id');
|
|
|
|
select col_type_is('contact', 'contact_id', 'integer');
|
|
|
|
select col_not_null('contact', 'contact_id');
|
|
|
|
select col_has_default('contact', 'contact_id');
|
|
|
|
select col_default_is('contact', 'contact_id', 'nextval(''contact_contact_id_seq''::regclass)');
|
|
|
|
|
|
|
|
select has_column('contact', 'company_id');
|
|
|
|
select col_is_fk('contact', 'company_id');
|
|
|
|
select fk_ok('contact', 'company_id', 'company', 'company_id');
|
|
|
|
select col_type_is('contact', 'company_id', 'integer');
|
|
|
|
select col_not_null('contact', 'company_id');
|
|
|
|
select col_hasnt_default('contact', 'company_id');
|
|
|
|
|
|
|
|
select has_column('contact', 'slug');
|
|
|
|
select col_is_unique('contact', 'slug');
|
|
|
|
select col_type_is('contact', 'slug', 'uuid');
|
|
|
|
select col_not_null('contact', 'slug');
|
|
|
|
select col_has_default('contact', 'slug');
|
|
|
|
select col_default_is('contact', 'slug', 'gen_random_uuid()');
|
|
|
|
|
Split contact relation into tax_details, phone, web, and email
We need to have contacts with just a name: we need to assign
freelancer’s quote as expense linked the government, but of course we
do not have a phone or email for that “contact”, much less a VATIN or
other tax details.
It is also interesting for other expenses-only contacts to not have to
input all tax details, as we may not need to invoice then, thus are
useless for us, but sometimes it might be interesting to have them,
“just in case”.
Of course, i did not want to make nullable any of the tax details
required to generate an invoice, otherwise we could allow illegal
invoices. Therefore, that data had to go in a different relation,
and invoice’s foreign key update to point to that relation, not just
customer, or we would again be able to create invalid invoices.
We replaced the contact’s trade name with just name, because we do not
need _three_ names for a contact, but we _do_ need two: the one we use
to refer to them and the business name for tax purposes.
The new contact_phone, contact_web, and contact_email relations could be
simply a nullable field, but i did not see the point, since there are
not that many instances where i need any of this data.
Now company.taxDetailsForm is no longer “the same as contactForm with
some extra fields”, because i have to add a check whether the user needs
to invoice the contact, to check that the required values are there.
I have an additional problem with the contact form when not using
JavaScript: i must set the required field to all tax details fields to
avoid the “(optional)” suffix, and because they _are_ required when
that checkbox is enabled, but i can not set them optional when the check
is unchecked. My solution for now is to ignore the form validation,
and later i will add some JavaScript that adds the validation again,
so it will work in all cases.
2023-06-30 19:32:48 +00:00
|
|
|
select has_column('contact', 'name');
|
|
|
|
select col_type_is('contact', 'name', 'text');
|
|
|
|
select col_not_null('contact', 'name');
|
|
|
|
select col_hasnt_default('contact', 'name');
|
2023-01-29 14:14:31 +00:00
|
|
|
|
Replace tag relations with array attributes
It all started when i wanted to try to filter invoices by multiple tags
using an “AND”, instead of “OR” as it was doing until now. But
something felt off and seemed to me that i was doing thing much more
complex than needed, all to be able to list the tags as a suggestion
in the input field—which i am not doing yet.
I found this article series[0] exploring different approaches for
tagging, which includes the one i was using, and comparing their
performance. I have not actually tested it, but it seems that i have
chosen the worst option, in both query time and storage.
I attempted to try using an array attribute to each table, which is more
or less the same they did in the articles but without using a separate
relation for tags, and i found out that all the queries were way easier
to write, and needed two joins less, so it was a no-brainer.
[0]: http://www.databasesoup.com/2015/01/tag-all-things.html
2023-04-07 19:31:35 +00:00
|
|
|
select has_column('contact', 'tags');
|
|
|
|
select col_type_is('contact', 'tags', 'tag_name[]');
|
|
|
|
select col_not_null('contact', 'tags');
|
|
|
|
select col_has_default('contact', 'tags');
|
|
|
|
select col_default_is('contact', 'tags', '{}');
|
|
|
|
|
2023-01-29 14:14:31 +00:00
|
|
|
select has_column('contact', 'created_at');
|
|
|
|
select col_type_is('contact', 'created_at', 'timestamp with time zone');
|
|
|
|
select col_not_null('contact', 'created_at');
|
|
|
|
select col_has_default('contact', 'created_at');
|
2023-06-15 11:55:15 +00:00
|
|
|
select col_default_is('contact', 'created_at', 'CURRENT_TIMESTAMP');
|
2023-01-29 14:14:31 +00:00
|
|
|
|
|
|
|
set client_min_messages to warning;
|
|
|
|
truncate contact cascade;
|
|
|
|
truncate company_user cascade;
|
2023-03-04 21:15:52 +00:00
|
|
|
truncate payment_method cascade;
|
2023-01-29 14:14:31 +00:00
|
|
|
truncate company cascade;
|
|
|
|
truncate auth."user" cascade;
|
|
|
|
reset client_min_messages;
|
|
|
|
|
2023-03-04 21:15:52 +00:00
|
|
|
set constraints "company_default_payment_method_id_fkey" deferred;
|
|
|
|
|
2023-01-29 14:14:31 +00:00
|
|
|
insert into auth."user" (user_id, email, name, password, role, cookie, cookie_expires_at)
|
|
|
|
values (1, 'demo@tandem.blog', 'Demo', 'test', 'invoicer', '44facbb30d8a419dfd4bfbc44a4b5539d4970148dfc84bed0e', current_timestamp + interval '1 month')
|
|
|
|
, (5, 'admin@tandem.blog', 'Demo', 'test', 'admin', '12af4c88b528c2ad4222e3740496ecbc58e76e26f087657524', current_timestamp + interval '1 month')
|
|
|
|
;
|
|
|
|
|
2023-03-04 21:15:52 +00:00
|
|
|
insert into company (company_id, business_name, vatin, trade_name, phone, email, web, address, city, province, postal_code, country_code, currency_code, default_payment_method_id)
|
|
|
|
values (2, 'Company 2', 'XX123', '', '555-555-555', 'a@a', '', '', '', '', '', 'ES', 'EUR', 222)
|
|
|
|
, (4, 'Company 4', 'XX234', '', '666-666-666', 'b@b', '', '', '', '', '', 'FR', 'USD', 444)
|
|
|
|
;
|
|
|
|
|
|
|
|
insert into payment_method (payment_method_id, company_id, name, instructions)
|
|
|
|
values (444, 4, 'cash', 'cash')
|
|
|
|
, (222, 2, 'cash', 'cash')
|
2023-01-29 14:14:31 +00:00
|
|
|
;
|
|
|
|
|
2023-03-04 21:15:52 +00:00
|
|
|
set constraints "company_default_payment_method_id_fkey" immediate;
|
|
|
|
|
2023-01-29 14:14:31 +00:00
|
|
|
insert into company_user (company_id, user_id)
|
|
|
|
values (2, 1)
|
|
|
|
, (4, 5)
|
|
|
|
;
|
|
|
|
|
Split contact relation into tax_details, phone, web, and email
We need to have contacts with just a name: we need to assign
freelancer’s quote as expense linked the government, but of course we
do not have a phone or email for that “contact”, much less a VATIN or
other tax details.
It is also interesting for other expenses-only contacts to not have to
input all tax details, as we may not need to invoice then, thus are
useless for us, but sometimes it might be interesting to have them,
“just in case”.
Of course, i did not want to make nullable any of the tax details
required to generate an invoice, otherwise we could allow illegal
invoices. Therefore, that data had to go in a different relation,
and invoice’s foreign key update to point to that relation, not just
customer, or we would again be able to create invalid invoices.
We replaced the contact’s trade name with just name, because we do not
need _three_ names for a contact, but we _do_ need two: the one we use
to refer to them and the business name for tax purposes.
The new contact_phone, contact_web, and contact_email relations could be
simply a nullable field, but i did not see the point, since there are
not that many instances where i need any of this data.
Now company.taxDetailsForm is no longer “the same as contactForm with
some extra fields”, because i have to add a check whether the user needs
to invoice the contact, to check that the required values are there.
I have an additional problem with the contact form when not using
JavaScript: i must set the required field to all tax details fields to
avoid the “(optional)” suffix, and because they _are_ required when
that checkbox is enabled, but i can not set them optional when the check
is unchecked. My solution for now is to ignore the form validation,
and later i will add some JavaScript that adds the validation again,
so it will work in all cases.
2023-06-30 19:32:48 +00:00
|
|
|
insert into contact (company_id, name)
|
|
|
|
values (2, 'Contact 1')
|
|
|
|
, (4, 'Contact 2')
|
2023-01-29 14:14:31 +00:00
|
|
|
;
|
|
|
|
|
|
|
|
prepare contact_data as
|
Split contact relation into tax_details, phone, web, and email
We need to have contacts with just a name: we need to assign
freelancer’s quote as expense linked the government, but of course we
do not have a phone or email for that “contact”, much less a VATIN or
other tax details.
It is also interesting for other expenses-only contacts to not have to
input all tax details, as we may not need to invoice then, thus are
useless for us, but sometimes it might be interesting to have them,
“just in case”.
Of course, i did not want to make nullable any of the tax details
required to generate an invoice, otherwise we could allow illegal
invoices. Therefore, that data had to go in a different relation,
and invoice’s foreign key update to point to that relation, not just
customer, or we would again be able to create invalid invoices.
We replaced the contact’s trade name with just name, because we do not
need _three_ names for a contact, but we _do_ need two: the one we use
to refer to them and the business name for tax purposes.
The new contact_phone, contact_web, and contact_email relations could be
simply a nullable field, but i did not see the point, since there are
not that many instances where i need any of this data.
Now company.taxDetailsForm is no longer “the same as contactForm with
some extra fields”, because i have to add a check whether the user needs
to invoice the contact, to check that the required values are there.
I have an additional problem with the contact form when not using
JavaScript: i must set the required field to all tax details fields to
avoid the “(optional)” suffix, and because they _are_ required when
that checkbox is enabled, but i can not set them optional when the check
is unchecked. My solution for now is to ignore the form validation,
and later i will add some JavaScript that adds the validation again,
so it will work in all cases.
2023-06-30 19:32:48 +00:00
|
|
|
select company_id, name
|
2023-01-29 14:14:31 +00:00
|
|
|
from contact
|
Split contact relation into tax_details, phone, web, and email
We need to have contacts with just a name: we need to assign
freelancer’s quote as expense linked the government, but of course we
do not have a phone or email for that “contact”, much less a VATIN or
other tax details.
It is also interesting for other expenses-only contacts to not have to
input all tax details, as we may not need to invoice then, thus are
useless for us, but sometimes it might be interesting to have them,
“just in case”.
Of course, i did not want to make nullable any of the tax details
required to generate an invoice, otherwise we could allow illegal
invoices. Therefore, that data had to go in a different relation,
and invoice’s foreign key update to point to that relation, not just
customer, or we would again be able to create invalid invoices.
We replaced the contact’s trade name with just name, because we do not
need _three_ names for a contact, but we _do_ need two: the one we use
to refer to them and the business name for tax purposes.
The new contact_phone, contact_web, and contact_email relations could be
simply a nullable field, but i did not see the point, since there are
not that many instances where i need any of this data.
Now company.taxDetailsForm is no longer “the same as contactForm with
some extra fields”, because i have to add a check whether the user needs
to invoice the contact, to check that the required values are there.
I have an additional problem with the contact form when not using
JavaScript: i must set the required field to all tax details fields to
avoid the “(optional)” suffix, and because they _are_ required when
that checkbox is enabled, but i can not set them optional when the check
is unchecked. My solution for now is to ignore the form validation,
and later i will add some JavaScript that adds the validation again,
so it will work in all cases.
2023-06-30 19:32:48 +00:00
|
|
|
order by company_id, name;
|
2023-01-29 14:14:31 +00:00
|
|
|
|
|
|
|
set role invoicer;
|
|
|
|
select is_empty('contact_data', 'Should show no data when cookie is not set yet');
|
|
|
|
reset role;
|
|
|
|
|
|
|
|
select set_cookie('44facbb30d8a419dfd4bfbc44a4b5539d4970148dfc84bed0e/demo@tandem.blog');
|
|
|
|
select bag_eq(
|
|
|
|
'contact_data',
|
|
|
|
$$ values (2, 'Contact 1')
|
|
|
|
$$,
|
|
|
|
'Should only list contacts of the companies where demo@tandem.blog is user of'
|
|
|
|
);
|
|
|
|
reset role;
|
|
|
|
|
|
|
|
select set_cookie('12af4c88b528c2ad4222e3740496ecbc58e76e26f087657524/admin@tandem.blog');
|
|
|
|
select bag_eq(
|
|
|
|
'contact_data',
|
|
|
|
$$ values (4, 'Contact 2')
|
|
|
|
$$,
|
|
|
|
'Should only list contacts of the companies where admin@tandem.blog is user of'
|
|
|
|
);
|
|
|
|
reset role;
|
|
|
|
|
|
|
|
select set_cookie('not-a-cookie');
|
|
|
|
select throws_ok(
|
|
|
|
'contact_data',
|
|
|
|
'42501', 'permission denied for table contact',
|
|
|
|
'Should not allow select to guest users'
|
|
|
|
);
|
|
|
|
reset role;
|
|
|
|
|
2023-02-17 11:39:32 +00:00
|
|
|
select throws_ok( $$
|
Split contact relation into tax_details, phone, web, and email
We need to have contacts with just a name: we need to assign
freelancer’s quote as expense linked the government, but of course we
do not have a phone or email for that “contact”, much less a VATIN or
other tax details.
It is also interesting for other expenses-only contacts to not have to
input all tax details, as we may not need to invoice then, thus are
useless for us, but sometimes it might be interesting to have them,
“just in case”.
Of course, i did not want to make nullable any of the tax details
required to generate an invoice, otherwise we could allow illegal
invoices. Therefore, that data had to go in a different relation,
and invoice’s foreign key update to point to that relation, not just
customer, or we would again be able to create invalid invoices.
We replaced the contact’s trade name with just name, because we do not
need _three_ names for a contact, but we _do_ need two: the one we use
to refer to them and the business name for tax purposes.
The new contact_phone, contact_web, and contact_email relations could be
simply a nullable field, but i did not see the point, since there are
not that many instances where i need any of this data.
Now company.taxDetailsForm is no longer “the same as contactForm with
some extra fields”, because i have to add a check whether the user needs
to invoice the contact, to check that the required values are there.
I have an additional problem with the contact form when not using
JavaScript: i must set the required field to all tax details fields to
avoid the “(optional)” suffix, and because they _are_ required when
that checkbox is enabled, but i can not set them optional when the check
is unchecked. My solution for now is to ignore the form validation,
and later i will add some JavaScript that adds the validation again,
so it will work in all cases.
2023-06-30 19:32:48 +00:00
|
|
|
insert into contact (company_id, name)
|
|
|
|
values (2, ' ')
|
2023-02-17 11:39:32 +00:00
|
|
|
$$,
|
Split contact relation into tax_details, phone, web, and email
We need to have contacts with just a name: we need to assign
freelancer’s quote as expense linked the government, but of course we
do not have a phone or email for that “contact”, much less a VATIN or
other tax details.
It is also interesting for other expenses-only contacts to not have to
input all tax details, as we may not need to invoice then, thus are
useless for us, but sometimes it might be interesting to have them,
“just in case”.
Of course, i did not want to make nullable any of the tax details
required to generate an invoice, otherwise we could allow illegal
invoices. Therefore, that data had to go in a different relation,
and invoice’s foreign key update to point to that relation, not just
customer, or we would again be able to create invalid invoices.
We replaced the contact’s trade name with just name, because we do not
need _three_ names for a contact, but we _do_ need two: the one we use
to refer to them and the business name for tax purposes.
The new contact_phone, contact_web, and contact_email relations could be
simply a nullable field, but i did not see the point, since there are
not that many instances where i need any of this data.
Now company.taxDetailsForm is no longer “the same as contactForm with
some extra fields”, because i have to add a check whether the user needs
to invoice the contact, to check that the required values are there.
I have an additional problem with the contact form when not using
JavaScript: i must set the required field to all tax details fields to
avoid the “(optional)” suffix, and because they _are_ required when
that checkbox is enabled, but i can not set them optional when the check
is unchecked. My solution for now is to ignore the form validation,
and later i will add some JavaScript that adds the validation again,
so it will work in all cases.
2023-06-30 19:32:48 +00:00
|
|
|
'23514', 'new row for relation "contact" violates check constraint "name_not_empty"',
|
|
|
|
'Should not allow contacts with blank trade name'
|
2023-02-17 11:39:32 +00:00
|
|
|
);
|
|
|
|
|
|
|
|
|
2023-01-29 14:14:31 +00:00
|
|
|
select *
|
|
|
|
from finish();
|
|
|
|
|
|
|
|
rollback;
|
|
|
|
|