Sqlstyle.guide Website Review

Deutsch (German) English 日本語 (Japanese) Português (BR) (Portuguese - Brazil) Русский (Russian) 简体中文 the key here is that you pick a style and stick to it. To suggest changes or fix bugs please open an issue These guidelines are designed to be compatible with Joe Celko’s SQL Programming Style easier. This guide is a little more opinionated in some areas and in others a little more relaxed. It is certainly more succinct where as a part of a project’s code base or reference it here for anyone on the project to freely read—much harder with a physical book. is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License The following suffixes have a universal meaning ensuring the columns can be read and understood easily from SQL code. Use the correct Always use uppercase for the reserved keywords like SELECT and WHERE. It is best to avoid the abbreviated keywords and use the full length ones where available (prefer ABSOLUTE to ABS). Do not use database server specific keywords where an ANSI SQL keyword already exists performing the same function. This helps to make code To make the code easier to read it is important that the correct complement of spacing is used. Do not crowd code or remove natural Spaces should be used to line up the code so that the root keywords all end on the same character boundary. This forms a river down the middle making it easy for the readers eye to scan over the code and separate the keywords from the implementation detail. Rivers are bad Notice that SELECT, FROM, etc. are all right aligned while the actual column names and implementation specific details are left aligned.  WHERE a.title = 'Charcoal Lane'     OR a.title = 'The New Danger'; Keeping all the keywords aligned to the righthand side and the values left aligned creates a uniform gap down the middle of query. It makes it much easier to scan the query definition over quickly too.  WHERE a.title = 'Charcoal Lane'     OR a.title = 'The New Danger';