Re: Justifying a PG over MySQL approach to a project

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: "Gauthier, Dave" <dave(dot)gauthier(at)intel(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org List" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Justifying a PG over MySQL approach to a project
Date: 2009-12-21 19:34:22
Message-ID: dcc563d10912211134g617d51ccjb899d48213ab4af9@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Dec 21, 2009 at 12:23 PM, Gauthier, Dave
<dave(dot)gauthier(at)intel(dot)com> wrote:
> They have ways to cope with this.  Since they all code in perl/DBI, they could simpy open handles to the 2 DBs.  Or there's an op sys level app out there that they could use to get the same data.  But I was thinking of something that would retain their ability to "join" into that data.

You can accomplish some stuff like that with dbilink. Not sure if
it's what you want or not.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Justin Alston 2009-12-21 21:04:12 unsubscribe
Previous Message Gauthier, Dave 2009-12-21 19:23:37 Re: Justifying a PG over MySQL approach to a project