Peter's Gekko

Sponsors

The Lounge

Syndication

Recent Posts

Tags

View more

News

Links

Archives

Advertisement

Peter's Gekko » Never name your table "project"
Images in this post missing? We recently lost them in a site migration. We're working to restore these as you read this. Should you need an image in an emergency, please contact us at imagehelp@codebetter.com
Never name your table "project"

I was working on two project management apps. For the same customer. In both apps I named the main table project. Dumb !!! Now the two apps are merging. The two project tables represent two different views on a (part of a) project. The code still works, namespaces and databases have to point out which view on a project I'm dealing with. But sometimes it's quite confusing. Lesson learned : “Don't give your tables general names”. Should be an open door :>

Peter

Posted 06-16-2004 8:43 AM by pvanooijen

[Advertisement]

Comments

Shannon J Hager wrote re: Never name your table "project"
on 06-16-2004 5:40 AM
what would your solution be? Instead of 2 "Project" tables, what would you name them if you had it to do over again?
Peter van Ooijen wrote re: Never name your table "project"
on 06-16-2004 6:05 AM
Something less general as "ProjektMOC" and "ProjektUitvoering" as the one deals with the "MOC" of the project and the other with the "uitvoering" of the project. But that's looking back. And later on the "uitvoering" might just as well split into several processes.
A real project table is emerging, it's glueing all the differnet aspects of a project together. But I couldn't name that one "projekt" as that name had allready been given out.

Add a Comment

(required)  
(optional)
(required)  
Remember Me?