Refactor Type System
From PostgreSQL wiki
(Difference between revisions)
(→Refactor the Type System) |
(→Refactor the Type System) |
||
| Line 3: | Line 3: | ||
ISSUES: | ISSUES: | ||
| - | + | Creaky typmod system | |
| - | - Need to store a separate entry for a type's array and other possible multiplicities | + | One 32-bit integer does not contain enough structure to describe |
| + | conveniently what a type should be. Pushing information into | ||
| + | userland, as PostGIS is forced to do, exposes these types to the | ||
| + | vicissitudes of user environment, search_path, etc. | ||
| + | |||
| + | Typmod is not preserved over all operations, leading to surprising | ||
| + | behavior. | ||
| + | |||
| + | Need to store a separate entry for a type's array and other possible multiplicities | ||
Revision as of 22:11, 12 November 2010
Refactor the Type System
ISSUES:
Creaky typmod system
One 32-bit integer does not contain enough structure to describe conveniently what a type should be. Pushing information into userland, as PostGIS is forced to do, exposes these types to the vicissitudes of user environment, search_path, etc.
Typmod is not preserved over all operations, leading to surprising behavior.
Need to store a separate entry for a type's array and other possible multiplicities
