It's not recommended since it might cause file locking issues internally.
how 'maybe' would that be? (that table almost never get written to, but when it is written to, the other one should be updated AFAP. both tables would almost never be written to at the same time)
Why not just set up a replication between those two servers and replicate the table?
becasue they are on the same machine, and IMHO replication would be a bit of an overkill for that, but i'd be happy to be corrected.
thanks,
M.
otherwise copying should work, but you'd still have some locking issues at the time of copying.
On Thu, 11 Dec 2003, Moritz von Schweinitz wrote:
hi there!
i have two databases on the same server, and one of the tables ('users') should be the same in both databases. since this is very specific to this one server, and other servers running similar databases don't need that functionality, i'm looking for the easiest way to do this, so i was wondering whether mysql is smart enough not to couse any mayor mess if i simply replace the users.* file in one of the datbase's directory with hardlinks to the other databses files for that table.
anyone know whether this works, and if not, what would be the easiest way of keeping two tables in differnt databases synced? a cronjob, maybe (it's not THAT time-critiva).
thanks,
M.
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
