#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 robe):
thinking further out loud, might be better to just have one history schema
(like there is only one pgtoast schema) and prefix the table name with the
original schema -- since creating more schemas may be equally confusing.
somthing like schema --> postgis_history
and tables would be postgis_history.public_mytable_history
the other side benefit of having a single history schema is I can exclude
it from backup since history can get very big very faast. I may only want
to backup the history once a week or month excluding from my regular
backup and that's trivial if its all isolated in a single schema.
Though I guess you'd have to deal with people moving their tables to
different schemas and renaming them. Then again maybe I should just shut
up.
--
Ticket URL: <
http://trac.osgeo.org/postgis/ticket/180#comment:11>
PostGIS <
http://trac.osgeo.org/postgis/>
PostGIS
_______________________________________________
postgis-devel mailing list
postgis-devel@...
http://postgis.refractions.net/mailman/listinfo/postgis-devel
