The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "GOCDB/PROM"
< GOCDB
Jump to navigation
Jump to search
m (Created page with 'This page is part of the GOCDB4 Architecture Documentation') |
m |
||
| Line 1: | Line 1: | ||
This page is part of the [[GOCDB4_Architecture|GOCDB4 Architecture Documentation]] | This page is part of the [[GOCDB4_Architecture|GOCDB4 Architecture Documentation]] | ||
== PROM (Pseudo-Relational Object Model) == | |||
The PROM is a database model implemented on top of a standard database. PROM's main goal is to facilitate schema changes, without affecting existing software that uses the database or the existing stored data. | |||
This is achieved by storing the relations in a set of database tables and enforcing these relations through an external API rather than querying the database directly. | |||
=== Objects: Groups of Data === | |||
Revision as of 11:33, 17 November 2010
This page is part of the GOCDB4 Architecture Documentation
PROM (Pseudo-Relational Object Model)
The PROM is a database model implemented on top of a standard database. PROM's main goal is to facilitate schema changes, without affecting existing software that uses the database or the existing stored data.
This is achieved by storing the relations in a set of database tables and enforcing these relations through an external API rather than querying the database directly.