This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Database with native ISO datatypes"
Jump to navigation
Jump to search
| Line 14: | Line 14: | ||
==PostgreSQL implementation== | ==PostgreSQL implementation== | ||
*Yeb Havinga and Willem Dijkstra implemented [[UDT]]'s in the PostgreSQL database management system, after a feasibility test with a few types in september '09 that turned out positive. | *Yeb Havinga and Willem Dijkstra implemented [[UDT]]'s in the PostgreSQL database management system, after a feasibility test with a few types in september '09 that turned out positive. | ||
| − | *As yet we did not perform comparative tests, though we expect the PostgreSQL implementation to outperform implementations in the application layer. | + | *As of yet we did not perform comparative tests, though we expect the PostgreSQL implementation to outperform implementations in the application layer. |
Revision as of 18:56, 17 January 2009
Summary
The ISO (or: Datatypes R2) data types can be implemented as 'native datatypes' at the database level. This may be an attractive option for RIMBAA applications.
Discussion
- It would be great to have an Ad Hoc query and don't bother with the details of e.g. a PQ.
- Grahame tried to implement UDT's in SQL-Server, but he did not like it because
- no support for inheritence/substituability
- the data is stored serialized as strings.
- very difficult to address nested content (lists/sets)
- Performance is an issue.
- There might be a problem with current ORM implementations witch cannot currently handle UDT's.
PostgreSQL implementation
- Yeb Havinga and Willem Dijkstra implemented UDT's in the PostgreSQL database management system, after a feasibility test with a few types in september '09 that turned out positive.
- As of yet we did not perform comparative tests, though we expect the PostgreSQL implementation to outperform implementations in the application layer.
