From: | Mark Wimer <mwimer(at)usgs(dot)gov> |
---|---|
To: | <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: connecting /sharing tables across databases |
Date: | 2008-11-19 18:17:23 |
Message-ID: | OF0A7FBEE5.0644ECC2-ON85257506.00600248-85257506.0064784E@usgs.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
In MSSQL, I have a dozen or so databases that rely on some shared tables
(states, species lists, for example). I put the shared tables in a db
called Common. To query them, mssql allows:
select statename, stateabbrev from common.dbo.statelist S inner join
mytable on S.stateabbrev = mytable.stateabbrev
I'm not asking for PostgreSQL to be more like mssql, but I would like to
share some lookup tables among applications & databases. In looking
through the help, it appears from the "Schemas" help page
(http://www.postgresql.org/docs/8.3/static/ddl-schemas.html) that
PostgreSQL uses a single database per connection (pgAdmin client, web
client). Is there a best practice or recommendation page for how to handle
this sharing of a common lookup table? Or a help page I missed that
discusses it?
Right now I see my options as:
a) put all applications for which I use PostgreSQL into one database, but
different schemas.
b) use a client tool to make a separate connection and create a join
afterwards
Thanks!
Mark
From | Date | Subject | |
---|---|---|---|
Next Message | Sean Davis | 2008-11-19 18:46:35 | Re: connecting /sharing tables across databases |
Previous Message | Tom Lane | 2008-11-19 17:56:51 | Re: ssl tunneling in postgres 8.1 |