| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | David Busby <busby(at)pnts(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Cross database foreign key workaround? |
| Date: | 2003-10-08 22:06:33 |
| Message-ID: | 3F848A69.4030705@joeconway.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
David Busby wrote:
> List,
> What are the recommended work arounds for cross database foreign keys?
> As I understand it transactions are not atomic with the TCL method. I have
> a situation that requires a master database and then a separate database for
> every subscriber. Subscribers need read/write to both databases. I chose
> separate databases because there are 20+ large tables that would require
> uid/gid columns, indexes and where conditions to separate information by
> subscriber. I thought that was too much overhead. Should I just use my
> application to make changes and ensure references that need to take place
> across databases? Or should I add a uid/gid to all necessary tables, create
> indexes and update all necessary where clauses? Ideas?
>
What about using schemas?
Joe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Elphick | 2003-10-08 22:10:20 | Re: Humor me: Postgresql vs. MySql (esp. licensing) |
| Previous Message | David Busby | 2003-10-08 21:46:15 | Cross database foreign key workaround? |