We're developing a management program that can manage several jobs that a construction company is working on. We have a separate database for each job that is installed in the program. This eliminates the need to keep an extra field in each table that designates which job the record is for. We simply have a connection open to the appropriate database that the user is working with. There are times that I wonder if this was an appropriate design, but for the most part, I think its the most simplistic way of coding it.
Matt
At 11:47 AM 1/8/2004, you wrote:
In our accounting software our users can manage the books for several different companies with the same program. As such I have to keep a field (in every record) that designates which company the given record is for and use it for report filtering, lookups, etc. Had I used a different database for each company then I would not need the overhead of this field. We chose the company field over the multiple databases because many of our clients are vertically integrated and do cross charging (an entry from one company posts to another company). This inter-company stuff is easy if the data is all in one database but we always have to remember to filter by the company field everywhere else. If I had it to do over again I'd probably use multiple databases.
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
