#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):
Hello pramsey. Thank you for all the info.
I tought of storing all history information on a separate schema, named
history (or whatever seems apropriate). All my functions are working in
history. Using a different schema is better? worse? I think this would be
better, since you can completely separate things.
About the naming of tables, rules and triggers: i sure can use a hand to
help me define a proper notation for this.
I will follow your advice about the overflow of history.
What about the current version attribute? Do you think it's a valuable
asset?
On a side note: i'm creating a table with geometry, and updating
geometry_columns, so the historic tables work on GIS softwares. Inserting
into geometry_columns is a good approach or i should drop column and
recreate it inside the historic table?
Thanks!
--
Ticket URL: <
http://trac.osgeo.org/postgis/ticket/180#comment:5>
PostGIS <
http://trac.osgeo.org/postgis/>
PostGIS
_______________________________________________
postgis-devel mailing list
postgis-devel@...
http://postgis.refractions.net/mailman/listinfo/postgis-devel
