#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 pramsey):
Current version attribute is not so useful for people, but can be quite
useful for software. Keep it around.
Updating geometry_columns yourself is acceptable.
I don't think a separate schema is wise, because for databases that
already have schema partitioning, you'll end up putting all the history
tables from different schemas into one place, potentially raising name
collisions, etc. I think a simple table naming scheme, either your 'h_'
one or a '_history' one (btw, I think 'history_' is better than 'h_', we
can spare the extra characters) is preferable.
--
Ticket URL: <
http://trac.osgeo.org/postgis/ticket/180#comment:6>
PostGIS <
http://trac.osgeo.org/postgis/>
PostGIS
_______________________________________________
postgis-devel mailing list
postgis-devel@...
http://postgis.refractions.net/mailman/listinfo/postgis-devel
