pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
sharing data accross several databases
3+ messages / 3 participants
[nested] [flat]

* sharing data accross several databases
@ 2002-01-22 12:50  bob lapique <lapique@chez.com>
  0 siblings, 1 reply; 3+ messages in thread

From: bob lapique @ 2002-01-22 12:50 UTC (permalink / raw)
  To: pgsql-sql

Hi,

I am designing 2 databases :
- the 1st relates to flasks
- the 2nd relates to cylinders

Both flasks and cylinders will be shipped accross the 
world and I need to keep track of check out dates, 
shipping method, destination, etc. These data will be of 
the same type for both databases.

Questions :
-----------
1) Is a 3rd database the solution ?
2) I would like to keep on using foreign keys (e.g. 
between a shipped item and the destination location)

Thanks for help.

-------------------
Vous aussi devenez le "Coup de coeur de Julie" et gagnez une Webcam
sur http://www.chez.com !
Chez.com vous invite à découvrir l'univers passionnant des sites persos.





^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: sharing data accross several databases
@ 2002-01-22 23:05  Josh Berkus <josh@agliodbs.com>
  parent: bob lapique <lapique@chez.com>
  0 siblings, 1 reply; 3+ messages in thread

From: Josh Berkus @ 2002-01-22 23:05 UTC (permalink / raw)
  To: bob lapique <lapique@chez.com>; pgsql-sql

Bob,
 
> I am designing 2 databases :
 > - the 1st relates to flasks
 > - the 2nd relates to cylinders
 > 
> Both flasks and cylinders will be shipped accross the 
> world and I need to keep track of check out dates, 
> shipping method, destination, etc. These data will be of 
> the same type for both databases.
 
So, why are you designing two seperate databases? It seems to me that
  you only need one database, with relevant tables carrying a "Type"
  column of "Flask" or "Cylinder". Seperate databases will give you all
  kinds of headaches you don't need.
 
> Questions :
 > -----------
 > 1) Is a 3rd database the solution ?
 
No. One, single, database is the solution.
 
> 2) I would like to keep on using foreign keys (e.g. 
> between a shipped item and the destination location)
 
PostgreSQL does not permit access of multiple databases from SQL (this
  was a design decision, based on the project's interpretation of the
  SQL92 standard). If you pursue you current approach, you will be
  forced to use middleware (such as JSP or J2EE or Perl::DBI) to access
  both of your databases at once ... considerable trouble for no
  benefit.
 
-Josh Berkus

______AGLIO DATABASE SOLUTIONS___________________________
                                       Josh Berkus
  Complete information technology      josh@agliodbs.com
   and data management solutions       (415) 565-7293
  for law firms, small businesses        fax 621-2533
    and non-profit organizations.      San Francisco



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: sharing data accross several databases
@ 2002-01-22 23:29  chester c young <chestercyoung@yahoo.com>
  parent: Josh Berkus <josh@agliodbs.com>
  0 siblings, 0 replies; 3+ messages in thread

From: chester c young @ 2002-01-22 23:29 UTC (permalink / raw)
  To: pgsql-sql

Absolutely agree!

> So, why are you designing two seperate databases? ...
> Seperate databases will give you all kinds of headaches you don't
need.



__________________________________________________
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!
http://promo.yahoo.com/videomail/



^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2002-01-22 23:29 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2002-01-22 12:50 sharing data accross several databases bob lapique <lapique@chez.com>
2002-01-22 23:05 ` Josh Berkus <josh@agliodbs.com>
2002-01-22 23:29   ` chester c young <chestercyoung@yahoo.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox