January 20, 2015 at 9:33 am
I've used product_id. I like typing code in all lowercase, both keywords and identifiers, which is ok so long as underscores are also used for clarity. Also, I don't have to maintain (or argue over) CamelCase consistency.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 20, 2015 at 9:47 am
Eric M Russell (1/20/2015)
I've used product_id. I like typing code in all lowercase, both keywords and identifiers, which is ok so long as underscores are also used for clarity. Also, I don't have to maintain (or argue over) CamelCase consistency.
But then you have to argue over using underscores in object names. That is one I don't care for because imho they are more difficult to type than standard capital letters. When the name is short like product_id it isn't too bad but when the names get longer the underscore makes it difficult to read.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
January 20, 2015 at 9:49 am
Sean Lange (1/20/2015)
Eric M Russell (1/20/2015)
I've used product_id. I like typing code in all lowercase, both keywords and identifiers, which is ok so long as underscores are also used for clarity. Also, I don't have to maintain (or argue over) CamelCase consistency.But then you have to argue over using underscores in object names. That is one I don't care for because imho they are more difficult to type than standard capital letters. When the name is short like product_id it isn't too bad but when the names get longer the underscore makes it difficult to read.
Says you. :rolleyes:
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 20, 2015 at 9:57 am
Eric M Russell (1/20/2015)
Sean Lange (1/20/2015)
Eric M Russell (1/20/2015)
I've used product_id. I like typing code in all lowercase, both keywords and identifiers, which is ok so long as underscores are also used for clarity. Also, I don't have to maintain (or argue over) CamelCase consistency.But then you have to argue over using underscores in object names. That is one I don't care for because imho they are more difficult to type than standard capital letters. When the name is short like product_id it isn't too bad but when the names get longer the underscore makes it difficult to read.
Says you. :rolleyes:
hehe. Naming standard are the worst. There is nothing that is perfect and are very subjective.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
January 20, 2015 at 11:08 am
Sean Lange (1/20/2015)
Eric M Russell (1/20/2015)
Sean Lange (1/20/2015)
Eric M Russell (1/20/2015)
I've used product_id. I like typing code in all lowercase, both keywords and identifiers, which is ok so long as underscores are also used for clarity. Also, I don't have to maintain (or argue over) CamelCase consistency.But then you have to argue over using underscores in object names. That is one I don't care for because imho they are more difficult to type than standard capital letters. When the name is short like product_id it isn't too bad but when the names get longer the underscore makes it difficult to read.
Says you. :rolleyes:
hehe. Naming standard are the worst. There is nothing that is perfect and are very subjective.
Bollocks. Mine is perfect. 😎
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
January 20, 2015 at 12:13 pm
Eric M Russell (1/20/2015)
which is ok so long as underscores are also used for clarity.
Underscores?!?!?! Heretic! Burn him!
:hehe:
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 20, 2015 at 1:25 pm
I don't care either way - intellisense types it for me.
MM
select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);January 21, 2015 at 3:39 am
I Use Id.No particular reason behind it
January 21, 2015 at 6:46 am
I use ID myself and like it. I think Id looks weird, as (in this context) it isn't a word, but maybe that's just me. I think the upper case ID in ProductID makes is stand out a bit more when reading it.
January 21, 2015 at 6:47 am
My databases are CI so I don't care 😛
Far away is close at hand in the images of elsewhere.
Anon.
January 21, 2015 at 7:04 am
... I think the upper case ID in ProductID makes is stand out a bit more when reading it.
To really stand out it should be named as:
pRODUCTiD
or even:
p-R-o-D-u-C-t_i-D
it fill flash into your eyes when reading...
😀
January 21, 2015 at 7:13 am
I use ID. It's an abbreviation that otherwise doesn't form a word.
January 21, 2015 at 7:16 am
ProductID, ProductId, and product_id are all respectable options, so long as it's done consistently.
However, I would take issue with ID by itself, on every table. Anytime I see that, I have low expectations for how the rest of the database is designed.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 21, 2015 at 7:19 am
I would take issue with ID by itself, on every table
Agreed. Maybe I should have made that clear in my post.
January 21, 2015 at 7:27 am
RonKyle (1/21/2015)
I use ID. It's an abbreviation that otherwise doesn't form a word.
... and ID is not? What is it then?
'Id' is an abbreviation of a single word and is therefore valid, at least in standard written English.
When abbreviating 'Company', would you write Co or CO?
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
Viewing 15 posts - 16 through 30 (of 103 total)
You must be logged in to reply to this topic. Login to reply