Steve,

Perhaps create a view? For example:

CREATE VIEW database1.somename AS SELECT * FROM database2.sometable;

Then you can get that info using:

SELECT * FROM database1.somename;

--
Ian Evans
Web Developer - eCommerce Team
University Book Store, Inc.
4326 University Way NE
Seattle, Washington 98105
206.634.3400 ext.621
[email protected]

On 3/14/2017 11:17 AM, Fogelson, Steve wrote:
> Over the years, I have written a pretty extensive shopping cart/back end
> processing application using TeraScript. The application handles
> multiple web sites with a separate MySQL database for each web site. All
> databases are running under one MySQL service with the One File per
> Table option enabled. This option makes InnoDB to store each created
> table into its own .ibd file.
>
>
>
> Each web site/database has an Inventory table. I would like to share the
> Inventory table from one site with another site. I use many JOINs and
> LEFT OUTER JOINs when reading the inventory table.
>
>
>
> I could look through all my tafs and tcfs for all INSERTS, UPDATES and
> DELETES, add code to update each other’s table and keep the separate
> Inventory tables identical, but I am looking for a better solution.
>
>
>
> I could pull the Inventory table out of the database and make the table
> it’s own database that both sites access, but I am not sure if JOINs and
> LEFT OUTER JOINs would work.
>
>
>
> Is there a way in MySQL to have one database look to another database
> for a table instead of it’s own?
>
>
>
> Or any other strategies you might recommend?
>
>
>
> Thanks in advance
>
>
>
> Steve Fogelson
>
> Internet Commerce Solutions
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------
> To unsubscribe from this list, please send an email to
> [email protected] <mailto:[email protected]> with
> "unsubscribe terascript-talk" in the body.


----------------------------------------

To unsubscribe from this list, please send an email to [email protected] 
with "unsubscribe terascript-talk" in the body.

<<attachment: ianev.vcf>>

Reply via email to