Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Naming conventions allow the development team to design discovereability and maintainability at the heart of the project. </p> <p>A good naming convention takes time to evolve but once it’s in place it allows the team to move forward with a common language. A good naming convention grows organically with the project. A good naming convention easily copes with changes during the longest and most important phase of the software lifecycle - service management in production.</p> <p>Here are my answers:</p> <ol> <li>Yes, table names should be plural when they refer to a set of <em>trades</em>, <em>securities</em>, or <em>counterparties</em> for example.</li> <li>Yes.</li> <li>Yes. SQL tables are prefixed with tb_, views are prefixed vw_, stored procedures are prefixed usp_ and triggers are prefixed tg_ followed by the database name.</li> <li>Column name should be lower case separated by underscore. </li> </ol> <p>Naming is hard but in every organisation there is someone who can name things and in every software team there should be someone who takes responsibility for namings standards and ensures that naming issues like <em>sec_id</em>, <em>sec_value</em> and <em>security_id</em> get resolved early before they get baked into the project.</p> <p>So what are the basic tenets of a good naming convention and standards: -</p> <ul> <li>Use the language of your client and your solution domain</li> <li>Be descriptive</li> <li>Be consistent</li> <li>Disambiguate, reflect and refactor</li> <li>Don’t use abbreviations unless they are clear to everyone</li> <li>Don’t use SQL reserved keywords as column names</li> </ul>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload