[PROJ] Performance when Auxilary DB used

[Even Rouault]

Le 31/08/2026 à 22:34, Weston Renoud a écrit :
> Hey Even,
>
> Removing the ORDER BY clause removed the need to materialize and gives 
> the same query performance as with the temporary tables, but without 
> the need to create any temporary tables which took extra time. Adding 
> back just the "ORDER BY score" still avoided the materialize, it 
> seemed to be the "usage.auth_name, usage.code" that triggered the 
> materialize. Are those necessary, or is "ORDER BY score" sufficient?

They are only necessary for reproducibility of results among SQLite 
versions, in case of equality of score.  There is no guarantee otherwise 
that different SQLite versions would return the same ordered result set. 
So they would need to be replicated on the C++ side ( std::sort() with 
an appropriate sort lambda)

-- 
http://www.spatialys.com
My software is free, but my time generally not.
LLMs contribute to global warming and brain rot.
Let's guillotine them! "Ah ! ça ira, ça ira, ça ira !"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/proj/attachments/20260831/7a42a518/attachment.htm>