Re: AW: Re: MySQL and BerkleyDB (fwd) - Mailing list pgsql-hackers

From The Hermit Hacker
Subject Re: AW: Re: MySQL and BerkleyDB (fwd)
Date
Msg-id Pine.BSF.4.31.0101221230470.644-100000@thelab.hub.org
Whole thread Raw
In response to AW: Re: MySQL and BerkleyDB (fwd)  (Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at>)
List pgsql-hackers
sounds like something that should be handled at the application level
though ... at least the concept of 'access to other db manufacturers' ...
no?


On Mon, 22 Jan 2001, Zeugswetter Andreas SB wrote:

>
> > Is anyone looking at doing this?  Is this purely a MySQL-ism, or is it
> > something that everyone else has except us?
>
> We should not only support access to all db's under one postmaster,
> but also remote access to other postmaster's databases.
> All biggie db's allow this in one way or another (synonyms,
> qualified object names) including 2-phase commit.
> Ideally this includes access to other db manufacturers, flat files, bdb ...
> Meaning, that this is a problem needing a generic approach.
>
> Andreas
>
> > > > Is there any possibility to get a port for MySQL with BerkleyDB support?
> > > > I realy need the transaction support and I'd like to build MySQL from a
> > > > port.
> > >
> > > why not just build PgSQL, and have transaction support *with* subselects
> > > and everything else that mySQL doesn't have?
> >
> > I'd *love* to use PgSQL, but it doesn't support cross-DB joins (or at
> > least I couldn't figure out how to do it.)  MySQL handles this, so
> > I'm using MySQL and would also like to have transaction support...
>

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: FW: Postgresql on win32
Next
From: Thomas Lockhart
Date:
Subject: Re: MySQL and BerkleyDB (fwd)