Home > Archive > MySQL ODBC Connector > September 2005 > Best way for maintaining a "master table" for use in several









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Best way for maintaining a "master table" for use in several
Neven Luetic

2005-09-27, 7:23 am

Hello,

I have a database scheme, containing a table, whichs content should be
unique across all databases with this scheme (on several servers as
well).

It would be possible to define one database, in which all changes would
be made. But what's the easiest way to keep the table consistent in the
other databases?

At the moment I can only think of reimporting the whole table in all
databases any time a change is made or when requested, what seems pretty
awkward. Perhaps triggers would be better, but I cannot switch to 5.0
(4.0 is used at the moment).

Any ideas?


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql? unsub...sie.nctu.edu.tw

Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2009 droptable.com