Knowing the rules that guide code development—known as Coding Standards—are important in a new project. Syntax is commonly covered in code reviews, but before reaching that stage, it is essential for the team to follow certain rules and conventions.
For the purposes of our discussion, we will address SQL, since this programming language is both specifically designed and commonly used for managing data in a relational database management system.
The “Coding Standards” is used to describe a wide range of guidelines in a coding project. This includes, for example, valid characters or functions. Having these guidelines prevents the project from having errors and returning undesired results, which come from having statements that are not structured properly.
Think of syntax as the manifestation or application of the desired logic in code.
This includes particular statements such as WHERE or UPDATE and clauses such as ON or ORDER BY.
Coding Standards may cover something as seemingly fundamental as declaring that a project will use ANSI Standard SQL.
Many database administrators may automatically assume Transact-SQL [T-SQL] is the same as Procedural Language [PL/SQL].
According to the ANSI/ISO/IEC International Standard , ANSI Standard SQL has several Language elements that compose its “Syntax”:
- Clauses: Which are constituent components of statements and queries.
- Expressions: Which can produce either scalar values, or tables consisting of columns and rows of data.
- Predicates: Which specify conditions that can be evaluated to SQL.
- Queries: Which retrieve the data based on specific criteria.
- Statements: Which may have a persistent effect on schemata and data, or may control transactions, program flow, connections, or sessions.
- Whitespace: Makes it easier to format SQL code for readability.
Coding Standards that relate to the database usually groups like below that may or may not have examples. Also I have seen a general statement such as:
“Use ANSI Standard SQL where applicable, all deviations or special cases seek approval from the appropriate manager prior to code review.”
Data Definition Language (DDL): Statements define the database structure or schema.
- CREATE: To create objects in the database
- ALTER: Alters the structure of the database
- DROP: Delete objects from the database
- TRUNCATE: Remove all records from a table, including all spaces allocated for the records.
- COMMENT: Add comments to the data dictionary
- RENAME: Rename an object
Data Manipulation Language (DML): Statements for managing data within schema objects.
- SELECT: Retrieve data from the a database
- INSERT: Insert data into a table
- UPDATE: Updates existing data within a table
- DELETE: Deletes records from a table
- MERGE: Operation
- EXPLAIN PLAN: Explain access path to data
- LOCK TABLE: Control concurrency
Data Control Language (DCL): Statements for managing access control
- GRANT: Gives user’s access privileges to database
- REVOKE: Withdraw access privileges given with the GRANT command
Transaction Control (TCL): Statements for managing transactions.
- COMMIT: Save work done
- SAVEPOINT: Identify a point in a transaction to which you can later roll back
- ROLLBACK: Restore database to original since the last COMMIT
- SET TRANSACTION: Change transaction options like isolation level and what rollback segment to use
The above is very basic and the actual Coding Standards can look very different. Depending on the rigidity of the coding standards; the location of comments, whitespace and indents may also be outlined.
You should now have some idea how the Coding Standards of an organization can aid you in your project code development effort. If you have questions about how to integrate these ideas into your operations, Datavail can work with you and your organization to effectively leverage SQL for your benefit and that of your clients and customers.
To learn more about our remote database services and how our experts can help with your ongoing SQL operations, please contact Datavail to discuss a custom solution designed for your enterprise.
Subscribe to Our Blog
Never miss a post! Stay up to date with the latest database, application and analytics tips and news. Delivered in a handy bi-weekly update straight to your inbox. You can unsubscribe at any time.
The “ORA-12154: TNS:could not resolve the connect identifier specified” Oracle error is a commonly seen message for database administrators.
EPM applications help measure the business performance. This post will help you choose the best EPM solutions for your organization’s needs and objectives.