Eli Ribble
97ec2c767d
I have to checkpoint this because I'm trying to get a very complicated multi-layered SQL query for inserting version history into the database and I need to improve it iteratively I've got a new binary that I can use to directly test complex stored procedures. This is to shorted my testing loop.
38 lines
1.2 KiB
SQL
38 lines
1.2 KiB
SQL
-- Table definition for fieldseeker.TreatmentArea
|
|
-- Includes versioning for tracking changes
|
|
|
|
CREATE SCHEMA IF NOT EXISTS fieldseeker;
|
|
|
|
CREATE TABLE fieldseeker.treatmentarea (
|
|
objectid BIGSERIAL NOT NULL,
|
|
treat_id UUID,
|
|
session_id UUID,
|
|
treatdate TIMESTAMP,
|
|
comments VARCHAR(250),
|
|
globalid UUID,
|
|
created_user VARCHAR(255),
|
|
created_date TIMESTAMP,
|
|
last_edited_user VARCHAR(255),
|
|
last_edited_date TIMESTAMP,
|
|
notified SMALLINT,
|
|
type VARCHAR(25),
|
|
creationdate TIMESTAMP,
|
|
creator VARCHAR(128),
|
|
editdate TIMESTAMP,
|
|
editor VARCHAR(128),
|
|
shape__area DOUBLE PRECISION,
|
|
shape__length DOUBLE PRECISION,
|
|
VERSION INTEGER NOT NULL DEFAULT 1,
|
|
PRIMARY KEY (objectid, VERSION)
|
|
);
|
|
|
|
COMMENT ON COLUMN fieldseeker.treatmentarea.VERSION IS 'Tracks version changes to the row. Increases when data is modified.';
|
|
|
|
COMMENT ON COLUMN fieldseeker.treatmentarea.treatdate IS 'Treatment Date';
|
|
|
|
-- See insert/insert_treatmentarea_versioned.sql for prepared insert statement
|
|
|
|
-- Usage notes for versioning:
|
|
-- When inserting a new row, VERSION defaults to 1
|
|
-- When updating a row, insert a new row with the same ID but incremented VERSION
|
|
-- The most recent version of a row has the highest VERSION value
|