From: | "Thomas T(dot) Thai" <tom(at)minnesota(dot)com> |
---|---|
To: | Alex Pilosov <alex(at)pilosoft(dot)com> |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Re: select to combine 2 tables |
Date: | 2001-06-23 04:12:31 |
Message-ID: | Pine.NEB.4.21.0106222312030.26565-100000@ns01.minnesota.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 22 Jun 2001, Alex Pilosov wrote:
> On Fri, 22 Jun 2001, Thomas T. Thai wrote:
>
> > > Huh? That *is* the generic, fully-SQL-standard way.
> >
> > the project i'm doing this for is opensource and i need it to work in both
> > postgresql and mysql. the above statement wouldn't work in mysql.
> MySQL is not a standards conforming database. You must not ask on
> postgresql list for a workaround against mysql brain-damage.
>
> Alternatively, the answer to your question (assuming you must get it to
> work on mysql and assuming that mysql does not understand the 'union'), is
> to do two separate queries on these tables and join them together in your
> perl code. But you knew that, right?
yes, but i was looking at the one query thing. i'm cheap! :)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-06-23 04:53:47 | Re: Multiple Indexing, performance impact |
Previous Message | Bruce Momjian | 2001-06-23 03:08:16 | Red Hat news hits Slashdot |