Hi (not subscribed to the list), i'm more or less maintaining sqlite3 in OpenBSD packages (at 3.28.0 now), and recently proj.4 was updated to a version that relies on sqlite3 to store projections, which has some constraints on values entered.
this broke on sparc64 (cf https://github.com/OSGeo/PROJ/issues/1508), because for some reason a float value gets converted to its opposite, which show simply with (per https://github.com/OSGeo/PROJ/issues/1508#issuecomment-500141325): >select 298.2564151; -298.2564151 of course, on OpenBSD/amd64 this simple sql statement works. So a bug in sqlite itself ? I don't have access to a sparc64 system right now, but i'd try previous sqlite versions to check for a regression. Landry _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
