View previous topic :: View next topic |
Author |
Message |
rickrat
Joined: 03 Oct 2007 Posts: 11
|
Posted: Mon Jul 28, 2008 3:02 am Post subject: Database Schema |
|
|
Ok, I've noticed that the database schema is ummm, different. For instance, there is multiple reserved words like the table "System" and table "Authentication". Meaning they have to be wrapped in [Authentication] instead of Authentication.
There is no primary key for the system table either.
Also, Primary Keys are "ID" instead of Microsoft Standard of "Id" If you generate code for DAL/OR Mapper, it will mark these and "not named according to standards". Plus it should be the name of the table too, like "ProductId" instead of just "Id".
I realize these are my personal preferences mostly, but I just thought I'd give you some heads up on some of it. |
|
Back to top |
|
|
Infralution
Joined: 28 Feb 2005 Posts: 5027
|
Posted: Mon Jul 28, 2008 4:57 am Post subject: |
|
|
The License Tracker table names are partly a result of history. Reserved words (beyond standard SQL reserved word) are database specific. These table names were not reserved words for JET which was the original database for License Tracker. As you point out this issue can be avoided when using other database engines by using [] to wrap the table names.
We don't use DAL/OR Mapper so their naming conventions haven't been an issue for us. I personally don't like code generation tools that force a particular naming convention on you. _________________ Infralution Support |
|
Back to top |
|
|
rickrat
Joined: 03 Oct 2007 Posts: 11
|
Posted: Mon Jul 28, 2008 6:08 am Post subject: |
|
|
Infralution wrote: | The License Tracker table names are partly a result of history. Reserved words (beyond standard SQL reserved word) are database specific. These table names were not reserved words for JET which was the original database for License Tracker. As you point out this issue can be avoided when using other database engines by using [] to wrap the table names.
We don't use DAL/OR Mapper so their naming conventions haven't been an issue for us. I personally don't like code generation tools that force a particular naming convention on you. |
I actually typed it wrong, I meant when you use a dal to generate classes or write classes manually, Microsoft Code Analysis don't like "ID", it likes "Id" I don't know why.
The .net framework is famous for having classes that follow coding guidelines and naming, and some that don't. |
|
Back to top |
|
|
|