Subject | Multi-level name space |
---|---|
Author | Jim Starkey |
Post date | 2006-01-12T20:35:31Z |
No single feature would make me happier than a multilevel name space.
The question is how to implement one without rewriting the database from
scratch.
Here is a modest proposal, more or less off the top of my header:
1. We increase the size of RDB$RELATION_NAME from 31 to 256 bytes
(and make it a varchar, this time, please).
2. Schemas are undeclared, just used (this is topic for debate, folks)
3. A qualified table name is represented in the system tables as
<schema>.<tablename> as in "myschema.mytable"
4. When fetching tables, we parse the table name, look for the dot,
and consider the prefix the schema name, the suffix the table name
5. In BLR we recognize and parse table names containing dots as
qualified names
Almost nothing changes except the max length of table names and the name
matching rules in the BLR and SQL compilers.
It seems too simple. What am I missing?
--
Jim Starkey
Netfrastructure, Inc.
978 526-1376
The question is how to implement one without rewriting the database from
scratch.
Here is a modest proposal, more or less off the top of my header:
1. We increase the size of RDB$RELATION_NAME from 31 to 256 bytes
(and make it a varchar, this time, please).
2. Schemas are undeclared, just used (this is topic for debate, folks)
3. A qualified table name is represented in the system tables as
<schema>.<tablename> as in "myschema.mytable"
4. When fetching tables, we parse the table name, look for the dot,
and consider the prefix the schema name, the suffix the table name
5. In BLR we recognize and parse table names containing dots as
qualified names
Almost nothing changes except the max length of table names and the name
matching rules in the BLR and SQL compilers.
It seems too simple. What am I missing?
--
Jim Starkey
Netfrastructure, Inc.
978 526-1376