Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This issue will actually be fixed with the Ocean 2012.1 API. The workstep reference will not include the version number anymore: Both workstep and process serialization is cleaned up. Version number is not serialized (and not used on deserialization) and a UniqueId can be used instead of the type name.</p> <p>Here is an extract of the 2012.1 Ocean release notes on the subject.</p> <p>Process and Workstep Unique Id Namespace: <code>Slb.Ocean.Petrel.Workflow</code></p> <p>Processes and worksteps created through Ocean did not have a proper identifier until now. They were identified by their full type name including the version number which means that their identifier could change, for instance, if: - The version number of the plug-in assembly was increased (e.g. new plug-in install). - The process/workstep class was moved to a new assembly. - The namespace of the process/workstep class was changed. This could cause issues in Petrel such as the display of a “broken link” instead of the process name in the Favorites tree or a workstep appearing as "workstep not available" in the workflow editor.</p> <p>To solve this, Ocean has removed the version number from the process and workstep identifier and is delivering a new API to support a user defined identifier for custom processes and worksteps which will be unique across the Petrel application. Any process/workstep created through Ocean should now implement a unique identifier.</p> <p>Please refer to: - <code>Process.UniqueId</code> to define unique identifier for processes - <code>Workstep.UniqueId</code> to define unique identifier for worksteps. The new API also offers backward compatibility support for already serialized processes/worksteps and a few changes in the serialization logic. When a legacy project is being opened the old-style ids are automatically replaced by new ids during deserialization.</p> <p>Best Regards, Gaelle</p>
    singulars
    1. This table or related slice is empty.
    1. PORefactoring/renaming Ocean Workstep derivative classes
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USGETah
    1. USGaelle Abecassis
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORefactoring/renaming Ocean Workstep derivative classes
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks a lot - very helpful!
      singulars
      1. PO
      1. USRobert Schmidt
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload