Thanks for the information and quick fix.
On Tue, Aug 2, 2022 at 9:56 PM Even Rouault
wrote:
> For reference this was also filed as
> https://github.com/OSGeo/gdal/issues/6149
>
> Implementation pull request: https://github.com/OSGeo/gdal/pull/6152
>
> Le 01/08/2022 à 07:01, prashanti seri a écr
On Wed, 3 Aug 2022 at 02:25, Even Rouault wrote:
>
>
> Le 02/08/2022 à 09:42, Michael Sumner a écrit :
> > Is it possible to determine the default SQL dialect that will be used
> > in the C++ API?
>
> Short answer: no
>
> Long answer: for a driver that is backed by a SQL engine (SQLite, GPKG,
> P
very helpful, thank you very much. Quite a bit more to it than I thought.
Best, Mike
On Tue, Aug 2, 2022 at 7:27 PM Rahkonen Jukka <
jukka.rahko...@maanmittauslaitos.fi> wrote:
> Hi,
>
>
>
> About INDIRECT_SQLITE dialect, it is documented in
> https://gdal.org/user/sql_sqlite_dialect.html
>
>
Excellent, thanks very much.
Best, Mike
On Wed, 3 Aug 2022, 02:30 Even Rouault, wrote:
>
> Le 02/08/2022 à 18:25, Even Rouault a écrit :
> >
> > Le 02/08/2022 à 09:42, Michael Sumner a écrit :
> >> Is it possible to determine the default SQL dialect that will be
> >> used in the C++ API?
> >
>
Le 02/08/2022 à 18:25, Even Rouault a écrit :
Le 02/08/2022 à 09:42, Michael Sumner a écrit :
Is it possible to determine the default SQL dialect that will be
used in the C++ API?
Short answer: no
Long answer: for a driver that is backed by a SQL engine (SQLite,
GPKG, PG, MySQL, OCI, etc.
For reference this was also filed as
https://github.com/OSGeo/gdal/issues/6149
Implementation pull request: https://github.com/OSGeo/gdal/pull/6152
Le 01/08/2022 à 07:01, prashanti seri a écrit :
Team,
We are exporting a "TextPointGeometry" type feature using GDAL MapInfo
driver. Below is th
Le 02/08/2022 à 09:42, Michael Sumner a écrit :
Is it possible to determine the default SQL dialect that will be used
in the C++ API?
Short answer: no
Long answer: for a driver that is backed by a SQL engine (SQLite, GPKG,
PG, MySQL, OCI, etc.), it will default to the RDBMS SQL engine,
oth
Hi,
About INDIRECT_SQLITE dialect, it is documented in
https://gdal.org/user/sql_sqlite_dialect.html
“If the datasource is SQLite database (GeoPackage, SpatiaLite) then SQLite
dialect acts as native SQL dialect and Virtual Table Mechanism is not used. It
is possible to force GDAL to use Virtual
Thank you Nyall.
On Tue, 2 Aug 2022 at 00:43, Nyall Dawson wrote:
>
> That said, you may have some luck if you try setting the environment
> variable "OGR_SKIP=ODBC". That was required for a working mdbtools
> driver on older GDAL releases.
>
After running "export OGR_SKIP=ODBC", and " ogrinfo
Is it possible to determine the default SQL dialect that will be used in
the C++ API?
It seems like the logic to pivot on dialect choice is only available to
drivers internally (they know if they have one), so a map of formats is
enough - but I wonder if I'm missing an API hook.
Also, there appe
10 matches
Mail list logo
