The primary keys were integer only. So the issues was not caused by
nvarchar as Pkeys. The issue was with nvarchars in general. This behaviour
can be tested with ogr2ogr by converting a table into a geojson or CSV ->
you will see hieroglyphs for exported nvarchar fields.
Le lun. 10 déc. 2018 à
On Sun, 9 Dec 2018 at 03:11, kimaidou wrote:
>
> Hi Nyall,
>
> Thanks for your answer. I had already checked that the layers had integer
> primary keys. I have discovered that the "wrong" layers had "nvarchar"
> fields, instead of "varchar". We changed the types of the view fields from
>
Hi Nyall,
Thanks for your answer. I had already checked that the layers had integer
primary keys. I have discovered that the "wrong" layers had "nvarchar"
fields, instead of "varchar". We changed the types of the view fields from
nvarchar to varchar, and it solved the issue.
Cheers,
Michaël
Le
On Thu, 6 Dec 2018 at 05:37, kimaidou wrote:
>
> Thanks for your answers. I managed to connect with QGIS MSSQL native provider
> under my Debian box with the following steps
> https://gist.github.com/mdouchin/64f7733a3c4ecfe441f65d5529351a30
>
> I have a weird behaviour. For some layers, QGIS
Thanks for your answers. I managed to connect with QGIS MSSQL native
provider under my Debian box with the following steps
https://gist.github.com/mdouchin/64f7733a3c4ecfe441f65d5529351a30
I have a weird behaviour. For some layers, QGIS Desktop cannot display the
features attributes : the
On Sat, 17 Nov 2018 at 02:01, kimaidou wrote:
>
> Hi all,
>
> I am trying to connect to a MSSQL server from a QGIS installed in a Linux
> Debian Jessie computer.
> I have checked that the credentials are ok with the mssql-client from
> Microsoft:
>
> mssql-cli -S myserver -U carto -P *** -d
Hi Michaël,
My first guest is that you need to update your GDAL. I was able to
import MSSQL tables with GDAL 2.3.2. With previous versions, I was
getting those hieroglyphs too.
I've imported a MSSQL Server database to Postgresql that was written by
Geomedia.
To recover the geometry, I had to
Ok, I have progressed a little bit.
You have to rename the section in the odbcinst.ini file. QGIS and ogr2ogr
expects the section [SQL Server] and not [ODBC Driver 17 for SQL Server] as
written by Microsoft package.
Then I can use ogr2ogr to connect to my database and convert some table
with
