Andrea Aime wrote:
Jody Garnett ha scritto:
Andrea Aime wrote:
becomes non 0 when it is replaced (so revision==0 always represents
the "live" data). Having two columns is not bad, does having both
help you ask for data in a specific range? Or could we get by with
just a single column.
I'm doing performance tests now, to see how much performance I give
up by using my schema, especially on extracting the last revision, which
is the most common operation anyways.
Let's assume then you will measure and make the best choice - and move
on to another topic.
No need to measure Jody, a subquery adds an O(n) to the mix, so it would
make everything real slow... or I'm missing something... Chris,what do
you think, let's add another half a day to it and measure the single
version column performance too?
Let's just go with two for this prototype. We're more wanting to
experiment with the protocol and get things out there, it's not worth
over optimizing now, and I see no big downsides to having two columns.
If client implementors hate it then we can change it down the road.
Chris
Cheers
Andrea
!DSPAM:1003,456dd3e2316929771116852!
--
Chris Holmes
The Open Planning Project
http://topp.openplans.org
begin:vcard
fn:Chris Holmes
n:Holmes;Chris
org:The Open Planning Project
adr:;;377 Broadway, 11th Floor;New York;NY;10013;USA
email;internet:[EMAIL PROTECTED]
title:VP, Strategic Development
x-mozilla-html:FALSE
url:http://topp.openplans.org
version:2.1
end:vcard
-------------------------------------------------------------------------
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
