[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-bugs] [Gnumed-devel] Unhandled exception on Office > List bi
From: |
Busser, Jim |
Subject: |
Re: [Gnumed-bugs] [Gnumed-devel] Unhandled exception on Office > List bills |
Date: |
Thu, 19 Jul 2012 23:29:17 +0000 |
Actually, it's possible that
1) the original bill had been bootstrapped (together with a few patient-related
billed items, perhaps related to Kirk)
gnumed_v17=> select * from bill.bill ;
pk_audit | row_version | modified_when | modified_by | pk |
invoice_id | close_date | apply_vat |
fk_receiver_identity | fk_receiver_address | fk_doc
----------+-------------+-------------------------------+-------------+----+-----------------------------+-------------------------------+-----------+----------------------+---------------------+--------
1658952 | 0 | 2012-06-12 16:54:50.707435-07 | gm-dbo | 1 |
address@hidden | | t |
| |
and
2) that I had deleted those items via psql as part of cleaning out such "demo"
items and also cleaning out the reference table of billable items, and that I
had deleted the items without deleting the bill to which they were attached.
For me to have been able to do so, does a referential integrity attribute or
trigger warrant to be added to the table
bill.bill
??
gnumed_v17=> \d+ bill.bill
<snip>
Indexes:
"bill_pkey" PRIMARY KEY, btree (pk)
"bill_bill_uniq_invoice_id" UNIQUE, btree (invoice_id)
Check constraints:
"bill_bill_sane_invoice_id" CHECK (gm.is_null_or_blank_string(invoice_id)
IS FALSE)
"bill_bill_sane_recv_adr" CHECK (fk_receiver_address IS NOT NULL OR
close_date IS NULL)
Foreign-key constraints:
"bill_fk_doc_fkey" FOREIGN KEY (fk_doc) REFERENCES blobs.doc_med(pk) ON
UPDATE CASCADE ON DELETE SET NULL
"bill_fk_receiver_address_fkey" FOREIGN KEY (fk_receiver_address)
REFERENCES dem.lnk_person_org_address(id) ON UPDATE CASCADE ON DELETE RESTRICT
"bill_fk_receiver_identity_fkey" FOREIGN KEY (fk_receiver_identity)
REFERENCES dem.identity(pk) ON UPDATE CASCADE ON DELETE RESTRICT
Referenced by:
TABLE "bill.bill_item" CONSTRAINT "bill_item_fk_bill_fkey" FOREIGN KEY
(fk_bill) REFERENCES bill.bill(pk) ON UPDATE CASCADE ON DELETE RESTRICT
Triggers:
tr_bill_mod AFTER INSERT OR DELETE OR UPDATE ON bill.bill DEFERRABLE
INITIALLY IMMEDIATE FOR EACH ROW EXECUTE PROCEDURE
bill.trf_announce_bill_mod_no_pk()
zt_del_bill BEFORE DELETE ON bill.bill FOR EACH ROW EXECUTE PROCEDURE
audit.ft_del_bill()
zt_ins_bill BEFORE INSERT ON bill.bill FOR EACH ROW EXECUTE PROCEDURE
audit.ft_ins_bill()
zt_upd_bill BEFORE UPDATE ON bill.bill FOR EACH ROW EXECUTE PROCEDURE
audit.ft_upd_bill()
Inherits: audit.audit_fields
Has OIDs: no
-- Jim
Re: [Gnumed-bugs] [Gnumed-devel] Unhandled exception on Office > List bills, Karsten Hilbert, 2012/07/29