[GRASS5] [bug #3917] (grass) v.out.ogr: schema error with PostGIS (1.1.0)

[Request Tracker]

this bug's URL: http://intevation.de/rt/webrt?serial_num=3917
-------------------------------------------------------------------------

Subject: v.out.ogr: schema error with PostGIS (1.1.0)

Platform: GNU/Linux/i386
grass obtained from: Trento Italy site
grass binary for platform: Compiled from Sources

Hi,

using v.out.ogr within Spearfish to export "soils" to
PostgreSQL 8/PostGIS 1.1.0, I got the following messages:

v.out.ogr input=soils type=area \
          dsn="PG:host=localhost dbname=postgis user=neteler" \
          olayer=soils format=PostgreSQL

# (translated from German message):
NOTICE:  CREATE TABLE creates implizitly a sequence »soils_ogc_fid_seq« for the »serial«
-column »soils.ogc_fid«
NOTICE:  Invalid schema name - using current_schema()
BACKGROUND:  SQL-command »SELECT  AddGeometryColumn('', $1 , $2 , $3 , $4 , $5 , $6 )«
        PL/pgSQL function "addgeometrycolumn" line 4 at select into variables

Exporting to SHAPE first, then 
 shp2pgsql testogr.shp testogr postgis | psql postgis
didn't print such messages.

The table structure is:
postgis=# \d soils;
                                    Tabelle »public.soils«
    Spalte    |        Typ        |                         Attribute                   
--------------+-------------------+------------------------------------------------------------
 ogc_fid      | integer           | not null default nextval('public.soils_ogc_fid_seq'::text)
 wkb_geometry | geometry          |
 cat          | integer           |
 label        | character varying |
Check-Constraints:
    »enforce_srid_wkb_geometry« CHECK (srid(wkb_geometry) = 1)
    »enforce_dims_wkb_geometry« CHECK (ndims(wkb_geometry) = 2)
    »enforce_geotype_wkb_geometry« CHECK (geometrytype(wkb_geometry) = 'POLYGON'::text OR wkb_geometry IS NULL)

postgis=# \d soils_ogc_fid_seq
Sequenz »public.soils_ogc_fid_seq«
    Spalte     |   Typ
---------------+---------
 sequence_name | name
 last_value    | bigint
 increment_by  | bigint
 max_value     | bigint
 min_value     | bigint
 cache_value   | bigint
 log_cnt       | bigint
 is_cycled     | boolean
 is_called     | boolean

Probably something changes in PostgreSQL V8 or the new PostGIS?

Markus



-------------------------------------------- Managed by Request Tracker