[PROJ] Performance when Auxilary DB used

[Javier Jimenez Shaw]

Thanks Weston for https://github.com/OSGeo/PROJ/pull/4833
It will be in PROJ 9.9.0!

For the people using auxiliary dbs (I know there is some people in this
list. Unfortunately I forgot their names), this is a great improvement.

On Mon, 31 Aug 2026 at 22:43, Even Rouault via PROJ <proj at lists.osgeo.org>
wrote:

>
> 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 !"
>
> _______________________________________________
> PROJ mailing list
> PROJ at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/proj
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/proj/attachments/20260901/aac68517/attachment.htm>