Details Ticket 5258


Comment | Reply | Open


Serial Number 5258
Subject v.patch: crash or ERROR, if tables missing in input
Area grass6
Queue grass
Requestors glorenz2000@yahoo.com
Owner mlanda
Status resolved
Last User Contact Thu Feb 22 13:54:04 2007 (2 yr ago)
Current Priority 30
Final Priority 70
Due No date assigned
Last Action Thu Feb 22 13:54:16 2007 (2 yr ago)
Created Sat Nov 4 16:28:24 2006 (2 yr ago)

Transaction History Ticket 5258


Sat, Nov 4 2006 16:28:24    Request created by guest  
Subject: v.in.region does not create db table (in postgresql)

Platform: GNU/Linux/x86
grass obtained from: CVS
grass binary for platform: Compiled from Sources
GRASS Version: 6.3cvs

Generating a new vector (area) file with the current region extent by the v.in.region
command does not create automatically a corresponding database table in PosgreSQL.
This results in errors when trying to rename the file or when using this vector
file in certain overlay procedures, such as v.patch and v.overlay, when table
contents should be inherited:

v.patch -e input=paguirre2006base4,testarea output=testpatch --overwrite
GRASS_INFO_ERROR(28119,1): Missing table


Manually creating a database table in PostgreSQL, connecting it to the vector
file (v.db.connect) and updloading the cat values is a simple workaround so far.
Sincerely,
Guido Lorenz
Universidad Nacional de Santiago del Estero
Argentina
Sun, Nov 5 2006 06:45:09    Mail sent by hamish_nospam@yahoo.com  
Return-Path <hamish_nospam@yahoo.com>
Delivered-To grass-bugs@lists.intevation.de
Date Sun, 5 Nov 2006 18:44:55 +1300
From Hamish <hamish_nospam@yahoo.com>
To Request Tracker <grass-bugs@intevation.de>
Cc grass-dev@grass.itc.it
Subject Re: [GRASS-dev] [bug #5258] (grass) v.in.region does not create db table (in postgresql)
Message-Id <20061105184455.5836636e.hamish_nospam@yahoo.com>
In-Reply-To <20061104152824.2322A101F00@lists.intevation.de>
References <20061104152824.2322A101F00@lists.intevation.de>
X-Mailer Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-pc-linux-gnu)
X-Face M<EoB)"*Z~u!,vFhXmw}R_KbdBta*P_=T|rbBL'e1/CQ9;/1g\BU3&!=y8ria$2Uk!HT&BB 8i?|X_+7~1jsy}F~g$2va%3fV`*=L(*cem[@3\yg,G,@rg6/QMJ
Mime-Version 1.0
Content-Type text/plain; charset=US-ASCII
Content-Transfer-Encoding 7bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-2.3 tagged_above=-999 required=3 tests=[BAYES_00=-5, FORGED_YAHOO_RCVD=2.7]
X-Spam-Level
> this bug's URL: http://intevation.de/rt/webrt?serial_num=5258
> ---------------------------------------------------------------------
> 
> Subject: v.in.region does not create db table (in postgresql)
..
> Generating a new vector (area) file with the current region extent by
> the v.in.region command does not create automatically a corresponding
> database table in PosgreSQL. This results in errors when trying to
> rename the file or when using this vector file in certain overlay
> procedures, such as v.patch and v.overlay, when table contents should
> be inherited:
> 
> v.patch -e input=paguirre2006base4,testarea output=testpatch
> --overwrite GRASS_INFO_ERROR(28119,1): Missing table
> 
> 
> Manually creating a database table in PostgreSQL, connecting it to the
> vector file (v.db.connect) and updloading the cat values is a simple
> workaround so far.


v.in.region creates a vector box -- it has no attributes that need
storing in a table.

I can't comment on PosgreSQL or deriative needs.


Hamish


Sun, Nov 5 2006 12:30:16    Subject changed to v.patch: crash or ERROR, if tables missing in input by msieczka  
Sun, Nov 5 2006 12:31:35    Mail sent by msieczka  
this bug's URL: http://intevation.de/rt/webrt?serial_num=5258

hamish_nospam@yahoo.com wrote (Sun, Nov 5 2006 06:45:09):

> Guido Lorenz wrote:

>> v.patch -e input=paguirre2006base4,testarea output=testpatch
>> --overwrite GRASS_INFO_ERROR(28119,1): Missing table
>>
>> Manually creating a database table in PostgreSQL, connecting it to the
>> vector file (v.db.connect) and updloading the cat values is a simple
>> workaround so far. 

> v.in.region creates a vector box -- it has no attributes that need
> storing in a table.

The problem is with v.patch. It will not work if used with -e while any of the
input vectors doesn't have a table. I'm renaming the bug.

> I can't comment on PosgreSQL or deriative needs.

This is not related to Postgres. With DBF it's the same.

Moreover, v.patch segfaults if used with -e while *neither* input vector has
a
table. See the follwoing examples:

in spearfish60:

$ v.random out=pt1 n=10
$ v.random out=pt2 n=10

### CASE 1: neither input vector has a table:

$ v.patch input=pt1,pt2 out=ptp -e
Segmentation fault (core dumped)
$ gdb v.patch core
(gdb) bt
#0  0x0804a29f in main (argc=0, argv=0xbfcdf604) at main.c:193
(gdb) q

### CASE 2: only one input vector doesn't have a table:

$ v.db.addtable pt1 columns="cat integer"
$ v.patch input=pt1,pt2 out=ptp -e
ERROR: Missing table

### CASE 3: both input vectors have a table:

$ v.db.addtable pt2 columns="cat integer"
$ v.patch input=pt1,pt2 out=ptp -e
(works)

Maciek
Thu, Feb 22 2007 13:27:17    Taken by mlanda  
Thu, Feb 22 2007 13:54:04    Mail sent by mlanda  
Fixed in CVS, closing the bug.
Thu, Feb 22 2007 13:54:16    Status changed to resolved by mlanda  
Comment | Reply | Open

You are currently authenticated as guest.
[Show Configuration] [Login as another user]

Users Guide - Mail Commands - Homepage of RequestTracker 1.0.7 - list any request