#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):
Just my two cents and should probably shut up on this. I woudl create a
differnt schema for history tables, kind of like how PostgreSQL has a
different schema for toast tables so as not to confuse people and
otherwise clutter the schema.
So if the user schema a table is in is say public, call the history schema
history_public or soem such thing.
I guess thinking out loud for my scenario -- I have say 150 tables in one
of my schemas -- most I would like to use this history feature. But I
won't, cause I don't want to wade thru 300 tables :)
history is a nice thing when you need to look at it interrorogate it, but
otherwise you want it to be abstracted away from your common workflow and
not to confuse unsuspecting users.
--
Ticket URL: <
http://trac.osgeo.org/postgis/ticket/180#comment:10>
PostGIS <
http://trac.osgeo.org/postgis/>
PostGIS
_______________________________________________
postgis-devel mailing list
postgis-devel@...
http://postgis.refractions.net/mailman/listinfo/postgis-devel
