Question Unprotected by Ramesh Rajendran
Question Protected by Ramesh Rajendran
deleted 2 characters in body
Source Link
ProfK
  • 50.2k
  • 124
  • 407
  • 783

ConventionAcademia has it that table names should be the singular of the entity that they store attributes of.

I dislike any T-SQL that requires square brackets around names, but I have renamed a Users table to the singular, forever sentencing those using the table to sometimes have to use brackets.

My gut feel is that it is more correct to stay with the singular, but my gut feel is also that brackets indicate undesirables like column names with spaces in them etc.

Should I stay, or should I go?

Convention has it that table names should be the singular of the entity that they store attributes of.

I dislike any T-SQL that requires square brackets around names, but I have renamed a Users table to the singular, forever sentencing those using the table to sometimes have to use brackets.

My gut feel is that it is more correct to stay with the singular, but my gut feel is also that brackets indicate undesirables like column names with spaces in them etc.

Should I stay, or should I go?

Academia has it that table names should be the singular of the entity that they store attributes of.

I dislike any T-SQL that requires square brackets around names, but I have renamed a Users table to the singular, forever sentencing those using the table to sometimes have to use brackets.

My gut feel is that it is more correct to stay with the singular, but my gut feel is also that brackets indicate undesirables like column names with spaces in them etc.

Should I stay, or should I go?

Question Unprotected by Adam Lear
Question Protected by Jon Ericson
Post Closed as "Opinion-based" by Adi Lester, Ry-
Post Made Community Wiki
Fixed grammar.
Source Link
ProfK
  • 50.2k
  • 124
  • 407
  • 783

Convention has it that table names should be the singular of the entity that they store attributes of.

I dislike any T-SQL that requirerequires square brackets around names, but I have renamed a Users table to the singular, forever sentencing those using the table to sometimes have to use brackets.

My gut feel is that it is more correct to stay with the singular, but my gut feel is also that brackets indicate undesirables like column names with spaces in them etc.

Should I stay, or should I go?

Convention has it that table names should be the singular of the entity that they store attributes of.

I dislike any T-SQL that require square brackets around names, but I have renamed a Users table to the singular, forever sentencing those using the table to sometimes have to use brackets.

My gut feel is that it is more correct to stay with the singular, but my gut feel is also that brackets indicate undesirables like column names with spaces in them etc.

Should I stay, or should I go?

Convention has it that table names should be the singular of the entity that they store attributes of.

I dislike any T-SQL that requires square brackets around names, but I have renamed a Users table to the singular, forever sentencing those using the table to sometimes have to use brackets.

My gut feel is that it is more correct to stay with the singular, but my gut feel is also that brackets indicate undesirables like column names with spaces in them etc.

Should I stay, or should I go?

added 15 characters in body; edited tags; edited title
Source Link
Michael Haren
  • 107.1k
  • 40
  • 170
  • 206

Table Naming Dilemma: Singular vs. Plural Names

Convention has it[1]it that table names should be the singular of the entity that they store attributes of. I

I dislike any T-SQL that require square brackets around names, but I have renamed a Users table to the singular, forever sentencing those using the table to sometimes have to use brackets. My

My gut feel is that it is more correct to stay with the singular, but my gut feel is also that brackets indicate undesirables like column names with spaces in them etc.

Should I stay, or should I go?

Table Naming Dilemma

Convention has it[1] that table names should be the singular of the entity that they store attributes of. I dislike any T-SQL that require square brackets around names, but I have renamed a Users table to the singular, forever sentencing those using the table to sometimes have to use brackets. My gut feel is that it is more correct to stay with the singular, but my gut feel is also that brackets indicate undesirables like column names with spaces in them etc.

Should I stay, or should I go?

Table Naming Dilemma: Singular vs. Plural Names

Convention has it that table names should be the singular of the entity that they store attributes of.

I dislike any T-SQL that require square brackets around names, but I have renamed a Users table to the singular, forever sentencing those using the table to sometimes have to use brackets.

My gut feel is that it is more correct to stay with the singular, but my gut feel is also that brackets indicate undesirables like column names with spaces in them etc.

Should I stay, or should I go?

Source Link
ProfK
  • 50.2k
  • 124
  • 407
  • 783
Loading