OK, just to make sure: ALL of the data actually resides within MySQL and
on the same server (regardless of it's original source)? That is good as
MySQL does not permit retrieving data from other servers in a query (yet).
So you have a table for the primary Model information, a second table for
the
"mel list_php" <[EMAIL PROTECTED]> wrote on 04/13/2005 11:07:44 AM:
>
>
> >
> >When you mention external databses, I got curious. Do you mean
"external"
> >as in "not on that MySQL server"? Or, do you mean "external" as in
"same
> >server, different database"?
> >
> >If you are designing your
When you mention external databses, I got curious. Do you mean "external"
as in "not on that MySQL server"? Or, do you mean "external" as in "same
server, different database"?
If you are designing your site correctly, the user should know nothing
about your data storage. That means that the "user"
> wants to look, so the search will be only a query to the dedicated table
> (database2 for ex if the user wants to retrieve articles)
>
> Do you think this kind of schema will be ok for the display of
information?
>
> Thank you very much for your time,
> Melanie
>
>
will be ok for the display of information?
Thank you very much for your time,
Melanie
From: "Gordon" <[EMAIL PROTECTED]>
To: "'mel list_php'" <[EMAIL PROTECTED]>,
Subject: RE: design: table depending on a column
Date: Tue, 12 Apr 2005 10:32:17 -0500
As
As long as articles.annotationID can be made distinct from
names.annotationID why not use 2 left joins.
You may have to test annotationType in the select section to map the fields.
Something like the following.
SELECT elements.annotationID,
CASE annotationType
WHEN 'names' T
