PostgreSQL naming conventions

后端 未结 2 814
半阙折子戏
半阙折子戏 2020-11-28 02:00

Where can I find a detailed manual about PostgreSQL naming conventions? (table names vs. camel case, sequences, primary keys, constraints, indexes, etc...)

相关标签:
2条回答
  • 2020-11-28 02:29

    Regarding tables names, case, etc, the prevalent convention is:

    • SQL keywords: UPPER CASE
    • names (identifiers): lower_case_with_underscores

    For example:

    UPDATE my_table SET name = 5;
    

    This is not written in stone, but the bit about identifiers in lower case is highly recommended, IMO. Postgresql treats identifiers case insensitively when not quoted (it actually folds them to lowercase internally), and case sensitively when quoted; many people are not aware of this idiosyncrasy. Using always lowercase you are safe. Anyway, it's acceptable to use camelCase or PascalCase (or UPPER_CASE), as long as you are consistent: either quote identifiers always or never (and this includes the schema creation!).

    I am not aware of many more conventions or style guides. Surrogate keys are normally made from a sequence (usually with the serial macro), it would be convenient to stick to that naming for those sequences if you create them by hand (tablename_colname_seq).

    See also some discussion here, here and (for general SQL) here, all with several related links.

    Note: Postgresql 10 introduced identity columns as an SQL-compliant replacement for serial.

    0 讨论(0)
  • 2020-11-28 02:34

    There isn't really a formal manual, because there's no single style or standard.

    So long as you understand the rules of identifier naming you can use whatever you like.

    In practice, I find it easier to use lower_case_underscore_separated_identifiers because it isn't necessary to "Double Quote" them everywhere to preserve case, spaces, etc.

    If you wanted to name your tables and functions "@MyAṕṕ! ""betty"" Shard$42" you'd be free to do that, though it'd be pain to type everywhere.

    The main things to understand are:

    • Unless double-quoted, identifiers are case-folded to lower-case, so MyTable, MYTABLE and mytable are all the same thing, but "MYTABLE" and "MyTable" are different;

    • Unless double-quoted:

      SQL identifiers and key words must begin with a letter (a-z, but also letters with diacritical marks and non-Latin letters) or an underscore (_). Subsequent characters in an identifier or key word can be letters, underscores, digits (0-9), or dollar signs ($).

    • You must double-quote keywords if you wish to use them as identifiers.

    In practice I strongly recommend that you do not use keywords as identifiers. At least avoid reserved words. Just because you can name a table "with" doesn't mean you should.

    0 讨论(0)
提交回复
热议问题