To put it simply, will bad things happen if I use a table name which is also a schema name.
For example:
Aircraft.Aircraft
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
To put it simply, will bad things happen if I use a table name which is also a schema name.
For example:
Aircraft.Aircraft
No reason why you can’t do this, as far as I know, though you may confuse yourself later. I suppose things might get sticky if you wrote queries that didn’t explicitly state the schema, but if you avoided doing that then you ought to be OK.
Having said that, I’d question the wisdom of doing this – to me, it suggests that either the schema name or the table name isn’t properly describing what it contains.