Database naming convention (ISO, RFC, etc.) for tables, columns, triggers, constraint, primary and foreign...
Who knows a naming convention (ISO, RFC o something like that) for tables, columns, triggers, constraints, primary and foreign keys to create a database in any database system (mysql, sql server, oracle, etc..).
For example i see databases with this naming conventions:
Naming Convention 1:
Table Name: Foo
Columns: Name, Description, IsEnabled
Naming Convention 2:
Table Name: foo
Columns: name, description, isenabled
Naming Convention 3:
Table Name: foo
Columns: name, description, is_enabled
Naming Convetion 4:
Table Name: Foo
Columns: FooName, FooDescription, FooIsEnabled
But i not find any ISO or RFC for this naming conventions or anothers naming conventions.
Thanks in advance
database
closed as primarily opinion-based by Mitch Wheat, Nick, AdrianHHH, leftjoin, darthbith Dec 30 '18 at 1:17
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
Who knows a naming convention (ISO, RFC o something like that) for tables, columns, triggers, constraints, primary and foreign keys to create a database in any database system (mysql, sql server, oracle, etc..).
For example i see databases with this naming conventions:
Naming Convention 1:
Table Name: Foo
Columns: Name, Description, IsEnabled
Naming Convention 2:
Table Name: foo
Columns: name, description, isenabled
Naming Convention 3:
Table Name: foo
Columns: name, description, is_enabled
Naming Convetion 4:
Table Name: Foo
Columns: FooName, FooDescription, FooIsEnabled
But i not find any ISO or RFC for this naming conventions or anothers naming conventions.
Thanks in advance
database
closed as primarily opinion-based by Mitch Wheat, Nick, AdrianHHH, leftjoin, darthbith Dec 30 '18 at 1:17
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
5
Pick one. Stick to it.
– Mitch Wheat
Jan 29 '18 at 14:25
add a comment |
Who knows a naming convention (ISO, RFC o something like that) for tables, columns, triggers, constraints, primary and foreign keys to create a database in any database system (mysql, sql server, oracle, etc..).
For example i see databases with this naming conventions:
Naming Convention 1:
Table Name: Foo
Columns: Name, Description, IsEnabled
Naming Convention 2:
Table Name: foo
Columns: name, description, isenabled
Naming Convention 3:
Table Name: foo
Columns: name, description, is_enabled
Naming Convetion 4:
Table Name: Foo
Columns: FooName, FooDescription, FooIsEnabled
But i not find any ISO or RFC for this naming conventions or anothers naming conventions.
Thanks in advance
database
Who knows a naming convention (ISO, RFC o something like that) for tables, columns, triggers, constraints, primary and foreign keys to create a database in any database system (mysql, sql server, oracle, etc..).
For example i see databases with this naming conventions:
Naming Convention 1:
Table Name: Foo
Columns: Name, Description, IsEnabled
Naming Convention 2:
Table Name: foo
Columns: name, description, isenabled
Naming Convention 3:
Table Name: foo
Columns: name, description, is_enabled
Naming Convetion 4:
Table Name: Foo
Columns: FooName, FooDescription, FooIsEnabled
But i not find any ISO or RFC for this naming conventions or anothers naming conventions.
Thanks in advance
database
database
asked Jan 29 '18 at 14:25
Eduardo Daniel MorónEduardo Daniel Morón
1111
1111
closed as primarily opinion-based by Mitch Wheat, Nick, AdrianHHH, leftjoin, darthbith Dec 30 '18 at 1:17
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as primarily opinion-based by Mitch Wheat, Nick, AdrianHHH, leftjoin, darthbith Dec 30 '18 at 1:17
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
5
Pick one. Stick to it.
– Mitch Wheat
Jan 29 '18 at 14:25
add a comment |
5
Pick one. Stick to it.
– Mitch Wheat
Jan 29 '18 at 14:25
5
5
Pick one. Stick to it.
– Mitch Wheat
Jan 29 '18 at 14:25
Pick one. Stick to it.
– Mitch Wheat
Jan 29 '18 at 14:25
add a comment |
1 Answer
1
active
oldest
votes
The best benchmark is togo with the default microsoft basic database:
https://github.com/Microsoft/sql-server-samples/releases/tag/adventureworks
in your case the naming convention should be CamelCase would be the perfect example, therefore go with the number 4:
Naming Convetion 4: Table Name: Foo Columns: FooName, FooDescription, FooIsEnabled
and stick to it as Mitch says :)
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The best benchmark is togo with the default microsoft basic database:
https://github.com/Microsoft/sql-server-samples/releases/tag/adventureworks
in your case the naming convention should be CamelCase would be the perfect example, therefore go with the number 4:
Naming Convetion 4: Table Name: Foo Columns: FooName, FooDescription, FooIsEnabled
and stick to it as Mitch says :)
add a comment |
The best benchmark is togo with the default microsoft basic database:
https://github.com/Microsoft/sql-server-samples/releases/tag/adventureworks
in your case the naming convention should be CamelCase would be the perfect example, therefore go with the number 4:
Naming Convetion 4: Table Name: Foo Columns: FooName, FooDescription, FooIsEnabled
and stick to it as Mitch says :)
add a comment |
The best benchmark is togo with the default microsoft basic database:
https://github.com/Microsoft/sql-server-samples/releases/tag/adventureworks
in your case the naming convention should be CamelCase would be the perfect example, therefore go with the number 4:
Naming Convetion 4: Table Name: Foo Columns: FooName, FooDescription, FooIsEnabled
and stick to it as Mitch says :)
The best benchmark is togo with the default microsoft basic database:
https://github.com/Microsoft/sql-server-samples/releases/tag/adventureworks
in your case the naming convention should be CamelCase would be the perfect example, therefore go with the number 4:
Naming Convetion 4: Table Name: Foo Columns: FooName, FooDescription, FooIsEnabled
and stick to it as Mitch says :)
answered Dec 29 '18 at 2:44
Tom BradleyTom Bradley
11
11
add a comment |
add a comment |
5
Pick one. Stick to it.
– Mitch Wheat
Jan 29 '18 at 14:25