[...]
Moritz:
> IIRC, if you use sqlitebrowser, you need to save your changes, before
> being able to access the db from GRASS.
The fact is that I couldn't do any changes to save them!
>
> BTW, has anyone compared sqlitebrowser to the sqlite manager add-on to
> firefox [1,2] ? After very rough
On 04/05/09 15:20, Nikos Alexandris wrote:
On Mon, 2009-05-04 at 15:07 +0200, Nikos Alexandris wrote:
[...]
Count another error here:
"Error in sqlite3_step():
database is locked"
All I am trying to do is:
v.what.rast vector=points raster=FINAL column=test
WoW :-O
All of a sudden, I can't
On Mon, May 4, 2009 at 3:20 PM, Nikos Alexandris
wrote:
> On Mon, 2009-05-04 at 15:07 +0200, Nikos Alexandris wrote:
>> [...]
>>
>> Count another error here:
>> "Error in sqlite3_step():
>> database is locked"
>>
>> All I am trying to do is:
>> v.what.rast vector=points raster=FINAL column=test
>
On Mon, 2009-05-04 at 15:07 +0200, Nikos Alexandris wrote:
> [...]
>
> Count another error here:
> "Error in sqlite3_step():
> database is locked"
>
> All I am trying to do is:
> v.what.rast vector=points raster=FINAL column=test
WoW :-O
All of a sudden, I can't copy vector maps, drop or add c
[...]
Count another error here:
"Error in sqlite3_step():
database is locked"
All I am trying to do is:
v.what.rast vector=points raster=FINAL column=test
Nikos
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/list
Dylan:
> Yeah. I have recently noticed this type of behavior after switching to
> sqlite. I was unable to patch two vectors (and att tables) after
> defining new columns of type varchar(20). I re-made the columns as
> 'text' and v.patch worked as expected. Maybe we need some special,
> internal con
Yeah. I have recently noticed this type of behavior after switching to
sqlite. I was unable to patch two vectors (and att tables) after
defining new columns of type varchar(20). I re-made the columns as
'text' and v.patch worked as expected. Maybe we need some special,
internal conversions (varchar
On 06/04/09 11:41, Moritz Lennert wrote:
On 03/04/09 17:06, Craig Leat wrote:
Moritz Lennert wrote:
Don't have time to look into this now, but it must be a problem in the
special sqlite implementation in that script:
if [ "$driver" = "sqlite" ] ; then
#echo "Using special trick for SQLi
On 03/04/09 17:06, Craig Leat wrote:
Moritz Lennert wrote:
Don't have time to look into this now, but it must be a problem in the
special sqlite implementation in that script:
if [ "$driver" = "sqlite" ] ; then
#echo "Using special trick for SQLite"
# http://www.sqlite.org/faq.htm
Moritz Lennert wrote:
> Don't have time to look into this now, but it must be a problem in the
> special sqlite implementation in that script:
>
> if [ "$driver" = "sqlite" ] ; then
>#echo "Using special trick for SQLite"
># http://www.sqlite.org/faq.html#q13
>v.info --q -c
On 03/04/09 11:34, Craig Leat wrote:
I have a problem with v.db.dropcol, it's changing the length of columns.
db.describe -c table=SBC1 driver=sqlite
database=/home/craig/GIS/grassdata/uMDM_ll/craig/sqlite.db
ncols: 6
nrows: 197842
Column 1: cat:INTEGER:20
Column 2: CLASS_NAME:CHARACTER:1
Column
I have a problem with v.db.dropcol, it's changing the length of columns.
db.describe -c table=SBC1 driver=sqlite
database=/home/craig/GIS/grassdata/uMDM_ll/craig/sqlite.db
ncols: 6
nrows: 197842
Column 1: cat:INTEGER:20
Column 2: CLASS_NAME:CHARACTER:1
Column 3: LM:CHARACTER:1
Column 4: WARD:INTEG
On Fri, Apr 3, 2009 at 10:59 AM, Moritz Lennert
wrote:
> On 03/04/09 10:03, Craig Leat wrote:
...
>> Can I change the length of
>> columns 2 and 3 in SBC1 and SBC2 or maybe I can copy the columns to
>> new columns with the correct length?
>
> AFAIK, sqlite does not support alter column statements,
On 03/04/09 10:03, Craig Leat wrote:
Moritz,
Thanks for the suggestions. I think I've got something:
Craig Leat wrote:
I am receiving the following error when patching two point vector maps:
v.patch -e in=SBC1,SBC2 out=SBC_0607
Patching vector map ...
DBMI-SQLite driver error:
Error in sqlite3
Moritz,
Thanks for the suggestions. I think I've got something:
Craig Leat wrote:
> I am receiving the following error when patching two point vector maps:
> v.patch -e in=SBC1,SBC2 out=SBC_0607
> Patching vector map ...
> DBMI-SQLite driver error:
> Error in sqlite3_step():
> SQL logic error or
On 03/04/09 09:10, Craig Leat wrote:
Moritz wrote:
What does v.db.connect -p show for each of the two maps ?
v.db.connect -p map=SBC1
Vector map is connected by:
layer <1> table in database
through driver
with key
v.db.connect -p map=SBC2
Vector map is connected by:
layer <1> table in
Moritz wrote:
> What does v.db.connect -p show for each of the two maps ?
v.db.connect -p map=SBC1
Vector map is connected by:
layer <1> table in database
through driver
with key
v.db.connect -p map=SBC2
Vector map is connected by:
layer <1> table in database
through driver
with key
Al
On 02/04/09 22:22, Craig Leat wrote:
I am receiving the following error when patching two point vector maps:
v.patch -e in=SBC1,SBC2 out=SBC_0607
Patching vector map ...
DBMI-SQLite driver error:
Error in sqlite3_step():
SQL logic error or missing database
ERROR: Cannot insert new record: 'inser
I am receiving the following error when patching two point vector maps:
v.patch -e in=SBC1,SBC2 out=SBC_0607
Patching vector map ...
DBMI-SQLite driver error:
Error in sqlite3_step():
SQL logic error or missing database
ERROR: Cannot insert new record: 'insert into SBC_0607 values ( 64510,
19 matches
Mail list logo
