Jody Garnett ha scritto: > Andrea wrote: >>> GetFeature >>> - so out of the box it returns the latest >>> >>> I am a bit concerned that making the revision columns available >>> messes up the origional schema (this simply will not work in the case >>> where the schema is provided by a third party authority for example). >>> Although this is not your use case (I recognize that) I am going to >>> work through how it can be done:
Oh, sleeping on things helps understanding. I finally realized that your suggestion about using version as a feature attribute is the only way to go, it just took a night to my bonehead to process it. The real problem in having version as an attribute in the schema is that I cannot limit the user to express only equality filters on top of it, he can make really any kind of filter he wants, and that would turn into a nightmare for me because with the two columns design encoding filters is real hard (and apparently the one column approach is not fast enough, see my other comment). Having it as an attribute forces people to use the revision number in the WFS 1.0 versioned extension, or the new version attribute in WFS 1.1, where you can _only_ express an equality comparison with a number (or say "ALL" in WFS 1.1 to gather all revisions of a feature). So, thank you muchly Jody, I wouldn't have realized this without your feedback :-) Cheers Andrea ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
