Search results

Page title matches

• GOCDB/PROM
  == PROM (Pseudo-Relational Object Model) == ...hips. This is because queries must repeatedly join across the core ‘admin’ PROM tables in order to determine those relationships before those objects can b
  9 KB (1,447 words) - 13:29, 18 December 2012
• PROM XML Data Interface
  #REDIRECT [[GOCDB/PROM XML Data Interface]]
  43 bytes (6 words) - 12:33, 20 December 2010
• GOCDB/PROM XML Data Interface
  == PROM XML Data Interface == This module is split up into two parts: PROM XML Input (obsolete) and PROM XML Output (obsolete as well).
  363 bytes (58 words) - 13:29, 18 December 2012

Page text matches

• GOCDB/PROM XML Data Interface
  == PROM XML Data Interface == This module is split up into two parts: PROM XML Input (obsolete) and PROM XML Output (obsolete as well).
  363 bytes (58 words) - 13:29, 18 December 2012
• GOCDB/Release4
  [[GOCDB/PROM |GOCDB PROM]]
  479 bytes (58 words) - 10:52, 19 December 2012
• PROM XML Data Interface
  #REDIRECT [[GOCDB/PROM XML Data Interface]]
  43 bytes (6 words) - 12:33, 20 December 2010
• GOCDB/Release4/Architecture
  ==== The PROM concept ==== ...odel, designed and architected by Peter Colclough, is described at [[GOCDB/PROM]].
  3 KB (473 words) - 10:52, 19 December 2012
• GOCDB/PROM
  == PROM (Pseudo-Relational Object Model) == ...hips. This is because queries must repeatedly join across the core ‘admin’ PROM tables in order to determine those relationships before those objects can b
  9 KB (1,447 words) - 13:29, 18 December 2012
• GOCDB/Release4/XML Input
  ...f_Data|PROM objects]] and [[GOCDB/PROM#Links_between_objects|links between PROM objects]] directly into the database. XML Input is most commonly used for C ...rvice endpoint entities. These entities are made up of a specific group of PROM objects linked together in a particular way. For example the service endpoi
  13 KB (1,888 words) - 13:33, 18 December 2012
• GOCDB/Relase4/XML Input/Entities/Service Endpoint
  Core PROM Object: '''service_endpoint'''
  908 bytes (126 words) - 13:30, 18 December 2012
• GOCDB/Release4/Development/v5
  * By replacing the PROM model with the [http://www.doctrine-project.org Doctrine ORM] GOCDB will su = v5 Benefits of changing the DB model (dropping PROM for doctrine) =
  8 KB (1,274 words) - 18:15, 30 September 2013
• GOCDB/Relase4/XML Input/Entities/Site
  Core PROM Object: '''site'''
  1 KB (199 words) - 13:30, 18 December 2012
• GOCDB/Release4/Regionalisation/Data Scoping
  <span lang="EN-GB">A PROM class called Tag If a site, SE or downtime has a PROM link to the EGI tag then the object
  6 KB (1,030 words) - 13:32, 18 December 2012
• GOCDB/Release4/DB Schema
  IMPORTANT NOTE: this DB schema is designed following a PROM model. You may want to check the page describing [[GOCDB/PROM]] first.
  8 KB (899 words) - 13:30, 18 December 2012
• GOCDB/Release4/Development/Recently Completed
  ** Refactored PROM db API. The underlying database code has been refactored considerably for g *** (Before v4.1, the GOCDB PROM API did not allow transaction demarcation in high level business operations
  8 KB (1,209 words) - 19:06, 6 November 2014
• EGI-InSPIRE:SA1 EGI Global tasks evolution
  * GOCDB v5 (~April/May). Replaces Oracle PROM database with ORM DB objects. Is needed to support different RDBMSs, improv
  45 KB (6,684 words) - 16:17, 6 January 2015