database design - best practices of separating two dependent sets of data in mysql -


my application needs 2 sets of data, , want separate logically on 2 parts. it's ideal have namespaces tables in 1 instance of mysql database, can't find clues feature exists. so, decided split data onto 2 schemas (static & dynamic) in 1 instance of mysql. though, dynamic data depends on static part, , of stored procedures in dynamic selects data static database.

what best practices avoid hardcoding schema names in stored procedures, or splitting data in similar way want?

this done synonyms, mysql not support that. didn't why wanted 'logically separate' data; done prefixing table names sort of identifier. avoid hassle of hard-coding schema names suggest rethinking separating tables.


Comments

Popular posts from this blog

c++ - Convert big endian to little endian when reading from a binary file -

C#: Application without a window or taskbar item (background app) that can still use Console.WriteLine() -

unicode - Are email addresses allowed to contain non-alphanumeric characters? -