R
Rob Fitzpatrick
Guest
Currently there is a fairly orderly numbering of tables in OpenEdge databases: >32767: SQL views >0: application tables -1 to -79: metaschema/SQL-89 views/physical structure -80 to -125: SQL catalog -200 to ?: audit/auth/logging -300 to -361?: MT/partitioning/DS <-16386: VSTs This isn't intended to be a comprehensive list but it illustrates the point. And importantly, all system table numbers are negative. This makes it possible to filter them in or out of a WHERE clause and still have a bracketed query. It also means a given range of CRUD stats (basetable to TRS), starting at 1, will contain only application tables. Index numbers, on the other hand, are a dog's breakfast. Positive numbers are given to application indexes, but also to some system indexes, from 1 to 7 and from 994 to 1093. And yet system index numbers from -1 to -1297 are unused. Many application databases contain more than 1000 indexes, meaning application indexes and system indexes are interspersed. This means users must accommodate system indexes when setting indexrangesize, allocating more shared memory than would otherwise be necessary if all system indexes had negative numbers. Also, when displaying index CRUD stats, users see a mix of system and application index data. These issues would be resolved if system indexes were numbered similarly to system tables, i.e. all with negative numbers.
Continue reading...
Continue reading...