s0c0 Posted November 6, 2007 Share Posted November 6, 2007 I initially began a project with my tables in database A, but when the amount of tables needed grew to 20+ I was told to create a new database. This sucked because I am inner joining on tables within database A, of course moving my tables to a new database broke several queries. Rather than creating objects to extract the data out of database A and work with my existing code our network administrator came up with an interesting solution. Since mysql stores tables as files within the databases folder on the file system, why not make a symbolic link to the tables. This is working for me in a development environment, but I am worried about potential problems that could arise from this. Has anyone on here tried this approach before? Any ideas on the possible downside of this? Quote Link to comment Share on other sites More sharing options...
fenway Posted November 6, 2007 Share Posted November 6, 2007 This seems like an inherently bad idea, fighting for locks and such... besides, you can always use federated tables. And who told you to make a new db. Quote Link to comment Share on other sites More sharing options...
s0c0 Posted November 6, 2007 Author Share Posted November 6, 2007 My boss told me to make the new DB...6 weeks plus into development. Yeah, I was real happy about that. If I may ask, what is a federated table? Quote Link to comment Share on other sites More sharing options...
fenway Posted November 7, 2007 Share Posted November 7, 2007 If I may ask, what is a federated table? Allows a local table to "be" a remote table -- see here. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.