My application is "growing" in the sense that I am finding more things that the complete database application should be able to accomplish for the user. Currently I have morphed into three "applications" which all have some common tables. I can see now that I should have started with a split database but that is hindsight which I need to now correct by figuring out how to update all the common tables and place into a back-end.
There are going to be quite a few tables by the time this is all finished. I need to organize them and name them in an efficient manner. I have created a DataTables folder to place them all into. I have created a "COMMON" subfolder, and a sub folder for each database application and am planning to place all the tables which are common to all the applications in the common folder. And then the tables which apply to only the one application in that applications folder. Is this the best approach to organizing the tables? Or is it best to place them all in a common folder and use a naming convention to organize them?
How do you name tables for best organization? I will have "set up" tables, "look up" tables and "transaction" tables. Do you use some convention for organizing table names? I am not referencing just the use of "tbl" as a prefix, rather some manner to group table names to make development more clear.
Does anyone use a numbering system to control the order of tables in the tables list? Or is that a bad idea?
__._,_.___
Posted by: david.pratt@outlook.com
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (1) |
Have you tried the highest rated email app?
With 4.5 stars in iTunes, the Yahoo Mail app is the highest rated email app on the market. What are you waiting for? Now you can access all your inboxes (Gmail, Outlook, AOL and more) in one place. Never delete an email again with 1000GB of free cloud storage.
.
__,_._,___
Tidak ada komentar:
Posting Komentar