(04-26-2017, 06:15 AM)Inori Wrote:

(04-26-2017, 06:00 AM)mothered Wrote: On a different scale, I was once trying to add a column with two separate words to my table (MySQL)  and completely forgot the "backticks", so the format was (for example):

Code:

PC Parts

but should have been:

Code:

`PC Parts`

That's why I use CamelCase for tables and columns; the less syntax I need to remember, the more I can focus on actually building my queries.

(04-26-2017, 06:31 AM)Ender Wrote:

(04-26-2017, 06:15 AM)Inori Wrote:

(04-26-2017, 06:00 AM)mothered Wrote: On a different scale, I was once trying to add a column with two separate words to my table (MySQL)  and completely forgot the "backticks", so the format was (for example):

Code:

PC Parts

but should have been:

Code:

`PC Parts`

That's why I use CamelCase for tables and columns; the less syntax I need to remember, the more I can focus on actually building my queries.

Hmm, many people disagree if it's CamelCase or if it's camelCase. Recently, I started using the camelCase style in my code instead of CamelCase style. (got this from java)

(04-26-2017, 06:43 AM)Inori Wrote:

(04-26-2017, 06:31 AM)Ender Wrote:

(04-26-2017, 06:15 AM)Inori Wrote: That's why I use CamelCase for tables and columns; the less syntax I need to remember, the more I can focus on actually building my queries.

Hmm, many people disagree if it's CamelCase or if it's camelCase. Recently, I started using the camelCase style in my code instead of CamelCase style. (got this from java)

Java's convention is CamelCase for classes, camelCase for everything else. C# usually follows CamelCase for namespaces, classes, and member functions, and SQL uses it for pretty much everything.

Not following those conventions isn't "wrong", it just might make the code a little more confusing to those who are used to it.