Re: Implementing "thick"/"fat" databases - Mailing list pgsql-general

From Chris Travers
Subject Re: Implementing "thick"/"fat" databases
Date
Msg-id CAKt_ZfuiC2_PBA8a+g0T1fBJ5OanSnjdjE0M+tKWWP91OCw-mw@mail.gmail.com
Whole thread Raw
In response to Re: Implementing "thick"/"fat" databases  (Chris Travers <chris.travers@gmail.com>)
List pgsql-general
> CREATE OR REPLACE FUNCTION payment_bulk_post
> (in_transactions numeric[], in_batch_id int, in_source text, in_total numeric,
>        in_ar_ap_accno text, in_cash_accno text,
>        in_payment_date date, in_account_class int, in_payment_type int,
>        in_exchangerate numeric, in_curr text)

Oh and as a disclaimer, this was tacked onto a database schema which
a) I did not design and b) is patently insane.  That part of the
database schema is being redesigned for 1.4.

Those wonderful disclaimers when having to post code against databases
designed by.... well better say nothing at all >:-D

Best Wishes,
Chris Travers

pgsql-general by date:

Previous
From: Chris Travers
Date:
Subject: Re: Implementing "thick"/"fat" databases
Next
From: Ilia Lilov
Date:
Subject: Re: Locking several tables within one transaction