From EGIWiki
Revision as of 14:03, 17 December 2012 by Jcasson (talk | contribs) (Benefits)
Jump to: navigation, search

<< Back to GOCDB/Release4/Development


By replacing the PROM model with the Doctrine ORM GOCDB will support RDBMSs other than Oracle.


  • Write code once, deploy to Oracle, MySQL, Postgres, SQLite.
  • Much simpler than the GOCDB/PROM model (see query comparison below)]
  • Easier for other projects to extend / modify
  • Easier for new developers to learn
  • Better performance
    • Reduced risk of failover performance issues
Doctrine SQL


The move to Doctrine will introduce changes to the GOCDB portal URLs and to the PRIMARY KEY, ID and GOCDB_PORTAL_URL fields of the GOCDB PI.

Portal URLs

In PROM, each "entity" (site, service endpoint, downtime) was assigned an ID from a global pool. There is only one object 123, the GRIDOPS-GOCDB site. The following URL is used to access an entity regardless of type:


In Doctrine, each entity receives an ID unique only to that entity type. There is a site with ID 123, a service endpoint with ID 123 and a downtime with ID 123. The new URL will reflect the entity type:




(...and so on for each GOCDB entity type)


PI Fields

In the GOCDB PI there are a number of PROM specific fields that will change if we move to Doctrine: PRIMARY_KEY, ID and GOCDB_PORTAL_URL. These are highlighted below:

Get Site Fields.png

The PRIMARY_KEY and ID fields are generated by PROM and will be either removed or replaced with similar values from Doctrine.

We would like to remove the ID field entirely and use the primary key only. The primary key will be purely numeric and unique only to the specific entity type (e.g. there will be a Site with ID 5 and a Service Endpoint with ID 5).

Request for Comments

If these changes affect a system that reads from the GOCDB-PI or links to the web portal please let us know.