November 15, 2012 at 12:55 pm
The "." is not part of the table name, it's the schema name.
You could check the Stairway for Database Design, it can give you an introduction to a naming convention.
I prefer underscores, but other prefer CamelCase, I'm unaware if there's a general rule but I've found that many things go by personal preference.
November 15, 2012 at 2:00 pm
Luis Cazares (11/15/2012)
The "." is not part of the table name, it's the schema name.You could check the Stairway for Database Design, it can give you an introduction to a naming convention.
I prefer underscores, but other prefer CamelCase, I'm unaware if there's a general rule but I've found that many things go by personal preference.
Ah thankyou, is using schemas a good idea? What are the benefits is it mainly for controlling security on objects ?
November 15, 2012 at 10:01 pm
bugg (11/15/2012)
Luis Cazares (11/15/2012)
The "." is not part of the table name, it's the schema name.You could check the Stairway for Database Design, it can give you an introduction to a naming convention.
I prefer underscores, but other prefer CamelCase, I'm unaware if there's a general rule but I've found that many things go by personal preference.
Ah thankyou, is using schemas a good idea? What are the benefits is it mainly for controlling security on objects ?
Schemas are great for implementing security but you can also use them as simple containers to categorize your objects and not utilize any of the security features if you do not need them:
Keep Schema and Ownership Simple by Dan Guzman
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 3 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply