Difference between revisions of "XMLDB key and index naming"
|Line 18:||Line 18:|
* MSSQL: 128 cc.
* MSSQL: 128 cc.
So, as the
So, as the number decides, we must be able to name everything in 30 cc. or less.
Revision as of 23:20, 9 August 2006
Every object in the DB have its own name. It's easy to know about table names and field names, but other objects, like keys, indexes, sequences... are created with some names difficult to know/understand. This page will try to explain a bit how all those objects will be named by the XMLDB generators in a compressive way.
First of all, you should know that, under the XMLDB Schema files everything is named easily, mainly because there are some exact conventions to follow. Basically, every key and index is named with one string that is the result of concatenating all the field names in the object, separated by "-". So, if we have one index over the fields "fieldA" and "fieldB" the index, in the XMLDB Files will be named "fieldA-fieldB". Simple!
But these resulting names aren't going to be the final names used to create the DB structure by the XMLDB generators. There we'll follow one nomenclature widely used by a lot of DB applications, that provides us with:
- One standard naming convention.
- The ability to know what's wrong when some key/index is throwing any error.
- The capability to have multiple Moolde servers running under the same DB.
Also, note that all these rules will be applied automatically by the XMLDB generators, so the object will be created with their correct names and you won't need to use such names directly, but under some special circumstances.
Also, every RDBMS has its own limit about the maximum length of such names. They are:
- MySQL: 64 cc.
- PostgreSQL: 32 cc. (64 under 8.0)
- Oracle: 30 cc.
- MSSQL: 128 cc.
So, as the smallest number decides, we must be able to name everything in 30 cc. or less.