Opened 16 years ago

Closed 16 years ago

Last modified 15 years ago

#959 closed defect (fixed)

Windows Vista - Error saving project - missing datasource params at qgs file

Reported by: luigibr Owned by: nobody
Priority: critical: causes crash or data corruption Milestone:
Component: Project Loading / Saving Version: 0.9.1
Keywords: project loading Cc:
Must Fix for Release: No Platform: Windows
Platform Version: Vista Awaiting user input: no

Description

I use qgis 0.91 for windows avaliable at www.qgis.org I have a project with 4 postgis layer's. I do some thematic work and save the project. When i was loading that project, a message appers saying that some layer's cannot be found. So I open the project file (*.qgs) and the information about the schema was missing at node datasource (inside maplayer node). To correct the file, i write the information and the project open without problems. So i think the problem is when the QGIS write the information about db connection at project file (qgs file).


.....
 <projectlayers layercount="4" >
        <maplayer minScale="1" maxScale="1e+08" scaleBasedVisibilityFlag="0" geometry="Point" type="vector" >
            <id>_public___table_v2___the_geom___sql_20080226164351311</id>
            <datasource>dbname=db host=192.168.0.100 port=5432 user=postgres password='******' table=*here-is-missing-the-squema*"table_v2" (the_geom) sql=</datasource>
            <layername>table_v2</layername>
            <srs>  
............


and


.....
 <projectlayers layercount="4" >
        <maplayer minScale="1" maxScale="1e+08" scaleBasedVisibilityFlag="0" geometry="Point" type="vector" >
            <id>_public___table_v2___the_geom___sql_20080226164351311</id>
            <datasource>dbname=db host=192.168.0.100 port=5432 user=postgres password='******' table="public"."table_v2" (the_geom) sql=</datasource>
            <layername>table_v2</layername>
            <srs> 
...

i put "public". before "table_v2" at table description.

Change History (4)

comment:1 by pcav, 16 years ago

Milestone: Version 0.9.2

in reply to:  description comment:2 by marcopx, 16 years ago

Replying to luigibr:

I use qgis 0.91 for windows avaliable at www.qgis.org I have a project with 4 postgis layer's. I do some thematic work and save the project. When i was loading that project, a message appers saying that some layer's cannot be found. So I open the project file (*.qgs) and the information about the schema was missing at node datasource (inside maplayer node). To correct the file, i write the information and the project open without problems. So i think the problem is when the QGIS write the information about db connection at project file (qgs file).


.....
 <projectlayers layercount="4" >
        <maplayer minScale="1" maxScale="1e+08" scaleBasedVisibilityFlag="0" geometry="Point" type="vector" >
            <id>_public___table_v2___the_geom___sql_20080226164351311</id>
            <datasource>dbname=db host=192.168.0.100 port=5432 user=postgres password='******' table=*here-is-missing-the-squema*"table_v2" (the_geom) sql=</datasource>
            <layername>table_v2</layername>
            <srs>  
............


and


.....
 <projectlayers layercount="4" >
        <maplayer minScale="1" maxScale="1e+08" scaleBasedVisibilityFlag="0" geometry="Point" type="vector" >
            <id>_public___table_v2___the_geom___sql_20080226164351311</id>
            <datasource>dbname=db host=192.168.0.100 port=5432 user=postgres password='******' table="public"."table_v2" (the_geom) sql=</datasource>
            <layername>table_v2</layername>
            <srs> 
...

i put "public". before "table_v2" at table description.

could you please test that bug with 0.11.0? Thanks,

Marco

comment:3 by luigibr, 16 years ago

Resolution: fixed
Status: newclosed

Hello Marco,

i have tested QGIS 0.11.0 with one postgis layer, one shp layer and one csv layer and all function without problem. I think the problem is solved.

Very thanks :D

comment:4 by (none), 15 years ago

Milestone: Version 1.0.0

Milestone Version 1.0.0 deleted

Note: See TracTickets for help on using tickets.