Sure, you right. I'm refering versioning in it's first meaning, that is, history tracking.
Thanks, Juan Pedro Pérez Alcántara On Wed, 2009-05-13 at 12:33 -0700, Paul Ramsey wrote: > Juan Pedro, > > What do you mean by "versioning"? > > History tracking? (Every state of the data is one version, but there > is only one branch of the data.) > Branching and merging? (People can take a copy of the data (a version) > and work on it, then merge it back into the main database.) > > Versioning is an overloaded word. Describe your actual use case. > > P. > > 2009/5/13 Juan Pedro Pérez Alcántara <[email protected]>: > > Hello all, > > > > soon we will face a project which will need a really strong versioning > > mechanism, including geometry. I'm sure anybody here have already > > addressed this sort of problem. I wonder if you can drop a line or two > > about this issue, for I consider it hard to implement. Sure the > > solutions will vary wildly depending on the scenario, the data, the > > versioning schedule, etc., but I'll be glad to hear about your > > experiences in that field. > > > > Greetings, > > > > Juan Pedro Pérez Alcántara > > > > > > _______________________________________________ > > postgis-users mailing list > > [email protected] > > http://postgis.refractions.net/mailman/listinfo/postgis-users > > > _______________________________________________ postgis-users mailing list [email protected] http://postgis.refractions.net/mailman/listinfo/postgis-users
