Editing nonversioned geodatabase data in PostgreSQL using SQL

You can use SQL to update, insert data into, and delete data from nonversioned tables in the geodatabase if they do not participate in geodatabase behavior. See What type of data can be edited using SQL? for information on the types of data and geodatabase behavior you cannot edit with SQL.

Note:

If the nonversioned table you want to edit using SQL is enabled for archiving, you must edit the table's archive view rather than the table itself. The view will automatically update certain ArcGIS-maintained fields. See What is an archive view and it's related topics for more information.

All data that is registered with the geodatabase has a system-maintained, unique, not-null ObjectID (Row ID) field. When you use SQL to insert records into nonversioned tables in the geodatabase, you must provide a unique value for the ObjectID. Include the Next_RowID function in an insert statement to populate the ObjectID field with the next valid value.

Note:

The next available ObjectID is not necessarily the next sequential number after the last inserted ObjectID. ObjectIDs for some client applications are assigned in batches, so the next available ObjectID may be many numbers higher than the last one you used. Also, any unused ObjectIDs from the batch are returned to the pool of available values, which means the next available ObjectID value may actually be a lower number than the one you inserted last.

This set of instructions describes updating one row at a time in a nonversioned table and inserting an ObjectID. You would most likely write a routine or client program to retrieve ObjectIDs and update your data.

Steps:

1. Log in to the database from an SQL editor such as psql.

   Be sure to log in to the database as a user who has permission to edit the data.

2. Use the Next_RowID function to populate the ObjectID field.

   In this example, the site_id column is the ObjectID field, the table is named outbreak, and it is stored in the hmoot schema.

   INSERT INTO hmoot.outbreak (site_id, med_code,num_affected, shape) 
    VALUES (
     sde.next_rowid('hmoot', 'outbreak'), 
     'v-22a', 
     3, 
     ST_Point('point (12 36))', 4326
    );
   

3. You can continue editing or, if you are done editing, commit your edits to the database.

If the table also contains a GUID or Global ID field, you must provide a unique value for this field as well. See Next_GlobalID for more information.