Link Details

Link 641249 thumbnail
User 317725 avatar

By cagdasbasaraner
via codebalance.blogspot.com
Published: Jul 25 2011 / 06:21

A compilation of database design best practices.
  • 54
  • 1
  • 7965
  • 284

Comments

Add your comment
User 352719 avatar

Jonathan Fisher replied ago:

0 votes Vote down Vote up Reply

Pretty solid advice (if you're using relational).

I always used Plural names for tables... Can someone shed some light why this might be bad?

User 431055 avatar

jfernandez replied ago:

0 votes Vote down Vote up Reply

I've always used plural names for tables (and underscores to separate words instead of using camel case). Just about every reference book I've read does as well. It makes sense to use plural names as tables don't hold only one piece of data.

User 393686 avatar

RawThinkTank replied ago:

0 votes Vote down Vote up Reply

TblSchool instead of just 'School' will make your complex queries readable.

And no TblSchools since its just one table.

User 352719 avatar

Jonathan Fisher replied ago:

0 votes Vote down Vote up Reply

I meant more like "Schools" instead of "School"

User 915511 avatar

vipul_vj replied ago:

0 votes Vote down Vote up Reply

Hey it's a really nice article and one of my favourites.

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Apache Hadoop
Written by: Piotr Krewski
Featured Refcardz: Top Refcardz:
  1. Play
  2. Akka
  3. Design Patterns
  4. OO JS
  5. Cont. Delivery
  1. Play
  2. Java Performance
  3. Akka
  4. REST
  5. Java