Thanks Yves!
We definitly have weird things, the query send by QGIS to define the cursor
is malformed, (no * in select, no commas between fields..)
In addition, we see several errors that should not exist. Qgis always
queries the style definition tbale even if it does not exists. QGis should
test
little update. We now reproduce the problem. It disappear when dropping the
primary key.
Yves, the DDL I gave you didn't have a PK, could you add one on id_anomlie
field and test?
Régis
--
View this message in context:
Régis,
Le lundi 26 mai 2014, 02:15:25 Régis Haubourg a écrit :
little update. We now reproduce the problem. It disappear when dropping the
primary key.
Yves, the DDL I gave you didn't have a PK, could you add one on id_anomlie
field and test?
Régis
pk_masse_eau_anomalie PRIMARY KEY, btree
OK, we have the problem each time we have a int primary key on a table, but
only in our production database. (pgpool2 + 2 pg replicating). dropping the
constraint restore normal behaviour
We are dumping the prod and restoring it in a new instance to check what
happens.
In QGIS provider
Régis,
I created the dce schema and the masse_eau_anomalie table inside. Added the
view and import some data from SQL request in your last email.
I have no problem when opening attribute table windows or using the identify
tools.
I am using QGIS master, with POSTGIS=2.1.2 r12389
Hi again,
my problem is unsolved. I eliminated either additionnal geometry column or
oid/ pk / select at id causes.
for a very simple postgis table, no way to open the attribute table, Qgis
freezes and transaction needs to be aborted on postgres side.
Any idea? Am I alone?
see table
Making a view from that table goes well.
I really don't have a clue.
see definition of the view
-- DROP VIEW dce.masse_eau_anomalie_ag;
CREATE OR REPLACE VIEW dce.masse_eau_anomalie_ag AS
SELECT id_anomalie, eu_cd, version_dce, description_anomalie,
date_signalement,
operateur,
Qgis 1.8 is concerned too. This is probably something on postgres side then.
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/qgis-freezes-when-opening-attribute-table-of-a-postgis-layer-without-key-value-tp5141587p5142186.html
Sent from the Quantum GIS - Developer mailing
We seem to have trouble with cursors.
here is postgres log when trying to open attribute table in qgis:
2014-05-23 17:56:51.885 CEST Quantum GIS 172.16.9.169(65371) 6153 idle in
transaction postgres refgeo2 ERROR: syntax error at or near FROM at
character 42
2014-05-23 17:56:51.885 CEST
other symptoms are that identify or select actions on map consider all
objects as one multi point.
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/qgis-freezes-when-opening-attribute-table-of-a-postgis-layer-without-key-value-tp5141587p5142193.html
Sent from the Quantum
QGIS 1.8 raises those error message :
2014-05-23T17:56:51: 1 cursor states lost.
SQL: DECLARE qgisf3 BINARY CURSOR FOR SELECT FROM
dce.masse_eau_anomalie
Résultat: 7 (ERROR: syntax error at or near FROM
LINE 1: DECLARE qgisf3 BINARY CURSOR FOR SELECT FROM dce.masse_e...
2014-05-23T17:56:52
QGIS 2.2 tries to create cursors infinitly.. when qgis 1.8 let first cursor
transaction idle.
Creating the table raw without any constraint in another schema works.
if anybody finds one day what happens, I'll be happy to learn..
Régis
--
View this message in context:
Hi,
I'm facing a severe bug in qgis 2.2 and master here.
I have layers defined in existing project that do not have a key in
datasource definition.
It seems that when a table has a oid field, postgis connection dialog does
not ask for a key field (it is a multi column primary key in that case).
Hi again,
I'm probably totally wrong in the previous analysis.
It seems that this is related to table with multiple geometry columns. Maybe
new attribute caching just can index additionnal geometry columns.
Anyway, this is still really severe. Anyone confirms?
--
View this message in
AFAIK the last postgres versione dismiss by default the oid.
Il 21/mag/2014 11:54 Régis Haubourg regis.haubo...@eau-adour-garonne.fr
ha scritto:
Hi,
I'm facing a severe bug in qgis 2.2 and master here.
I have layers defined in existing project that do not have a key in
datasource definition.
15 matches
Mail list logo