[postgis-devel] [PostGIS] #180: History table example implementation

[PostGIS]

#180: History table example implementation
--------------------------+-------------------------------------------------
  Reporter:  pramsey      |       Owner:  pimpaa       
      Type:  enhancement  |      Status:  assigned     
  Priority:  medium       |   Milestone:  postgis 1.5.0
 Component:  postgis      |     Version:               
Resolution:               |    Keywords:               
--------------------------+-------------------------------------------------
Comment (by pimpaa):

 Well, to change everyting to a dif schema inst hard at all.

 This is what i need, concerning user input. My first tought was to have a
 diferent schema, 'history'.

 This is a discussion that i would like to initiate. I'm here to help :D.

 history tables will get big pretty fast, since each update they create a
 new record. a new fucntion that i'm planning (and i need help, with
 sugestions) is to create indexes to the history_table. It´s little
 improvemente, but its a nice improvement. It´s not possible to recreate
 the indexes that are used on the original table because it will implicate
 in a primary key index in the "id" field.

 The "like" command provides this functionlaity, but i dont think its all
 that useful. It will cause more trouble then good.

 to pramsey: the spatial constraints are perhaps not needed, since they ARE
 veryfied in the parent table. i'll look into that.

 anyhow! i would like suggestions to improve the schema, tables, and
 everything.

 specifying a schema is useful, and not specifying is useful too, so we
 need to ponderate the benefits on over another.

 as i said, im open to suggestions, and theres is tons of improvements over
 this code. im just a begginer.

 thanks to all that had the patiete to go trought it and evaluate it.

 george

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/180#comment:12>
PostGIS <http://trac.osgeo.org/postgis/>
PostGIS