![]() ![]() Unless I misunderstood what I was reading, which may very well be the case. The one answer in the above links says to create many tables (many to many) while the other says to have 1 common table with multiple specific tables for the specific users (reports in my case). ![]() And of course, I'm running into at least 2 columns that are needed in this combined table that will have NULL values for some reports and not others. Basically it seems to be getting bigger than if I had used the much of the same code in each module with the exact tables and column names needed for that report. However I am ending up with a lot of code that identifies what tables to go look at depending on the report being used as well as other parameters. ![]() I was trying to use Object-oriented design by creating one table to store the common columns (createddate, createdby, reportnumber, title, etc). Each report has different inputs than the other. My problem: I have 4 reports to keep in a database (possibly more in the future). MySQL Question - How to handle multiple types of users - one table or multiple? I have read the answers to the following questions and I believe they point to two different answers:ĭatabase Design: Multiple tables vs a single table ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |