I have no idea whether PostGIS support is supposed to be functional in the
native Windows build. If it is not please disregard this message. In case it
is and no one else has noticed, I have not been able to load any PostGIS
(1.1.6 on PostgreSQL 8.1.5 Windows) geometries into the native Windows
builds, including the latest one. The program does connect and read the
database schema; I can enter filter conditions, preview column values,
execute preview queries -- the whole nine yards. But when I try to load the
geometries, I inevitably get an error message "public.xyz(the_geom) sql= is
an invalid layer and cannot be loaded." (same with an explicit WHERE

GRASS rasters don't load either, as someone else has already pointed out.

There is also a problem with PostgreSQL schema names that contain periods
(not only in the Windows build). Qgis apparently doesn't quote the schema.
If, for example, anyone uses their full name in the form
"firstname.lastname" as a schema name, which is perfectly legal in
PostgreSQL and perhaps not such a weird idea (cf. e-mail accounts), Qgis
won't be able to read the tables in that schema.

Let me close by saying that the visual style of the native Windows interface
is quite compelling and elegant. I like it a lot.

Thanks for all your hard work.
Cheers, Hartmut


Message: 1
Date: Wed, 29 Nov 2006 10:34:39 -0200
From: "Tim Sutton" <[EMAIL PROTECTED]>
Subject: [Qgis-user] Windows native build snapshot
To: qgis-developer <[EMAIL PROTECTED]>, qgis-user
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi All

I've uploaded another windows build snapshot (release version only) which
includes fixes to make the grass shell work again. Can someone who knows
more about grass than me have a quick test to see if the shell works as

Note for the shell to work QGIS still needs to intall in a base dir with no
spaces. i.e. installing into c:\Program Files\QuantumGIS will not allow
shell to work as the path has spaces in it.

The snapshot is available here:


The snapshot also includes a few other fixes like plugins showing up in the
plugin manager properly. The win build still has some issues so its not
building everything in the codebase properly yet. Thanks to Martin, Freddy
and Phillippe for the ongoing help! Anyone else who would like to help (even
if its just testing and filing bugs) please contact me. I'd be particularly
interested to hear from someone who can help get python setup in the msys
environment and test the ms_export tool.


Tim Sutton

Visit http://qgis.org for a great Open Source GIS Home Page:
Skype: timlinux
Jabber: timlinux
Irc: timlinux on #qgis at freenode.net

Qgis-user mailing list

Reply via email to