| From: | Chris Travers <chris(dot)travers(at)gmail(dot)com> |
|---|---|
| To: | Karl Nack <karlnack(at)futurityinc(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Implementing "thick"/"fat" databases |
| Date: | 2011-07-23 23:56:30 |
| Message-ID: | CAKt_ZfuiC2_PBA8a+g0T1fBJ5OanSnjdjE0M+tKWWP91OCw-mw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yan Chunlu | 2011-07-24 02:43:56 | Re: streaming replication does not work across datacenter with 20ms latency? |
| Previous Message | Chris Travers | 2011-07-23 23:51:02 | Re: Implementing "thick"/"fat" databases |