[GRASS5] db.oodbfedit: a _very_ simplistic approach to dbf
mlennert at club.worldonline.be
Fri Aug 5 12:45:23 EDT 2005
On Thu, August 4, 2005 21:38, Daniel Calvelo Aros said:
> From: Markus Neteler <neteler at itc.it>
> Sent: Thu, 4 Aug 2005 17:33:33 +0200
>> On Wed, May 25, 2005 at 02:30:41PM +0200, Markus Neteler wrote:
>> > On Wed, May 25, 2005 at 10:33:28AM +0200, Moritz Lennert wrote:
>> > ...
>> > > All these different elements contribute to the idea that finally my idea
>> > > wasn't so great ;-)
>> > > I'll pursue the other path of creating easy frontends to db.execute.
>> > Maybe things should go into sqlite3 direction (there are tcl/tk bindings),
>> > and/or OGR SQL engine.
>> > sqlite3 could be interesting to manage raster time series as well etc.
>> There is also a browser (or several):
This does look good, but it depends on QT. It seems a bit overkill to have
GRASS depend on QT just for a data browser...
This should be part of the general discussion of a future GRASS GUI that
Michael launched recently.
> BTW, Moritz, have you tried the current CVS for extended SQL capabilities?
> Please do so, and come up with wishes for extending it further. I've been
> griping with NULL/NAN handling, but have come up with nothing concrete yet.
Could you remind of what the new capabilities actually are, so that I know
what to test ?
Last time I asked, this was the answer from Glynn
> > Only a limited set of SQL functions and operators are currently supported.
> > Addition is not among them.
> > see the GRASS SQL help page:
> > http://grass.ibiblio.org/grass61/manuals/html61_user/sql.html
> Would the latest changes to the sql expression parser
> (http://grass.itc.it/pipermail/grass5/2005-June/018588.html and
> following) change this ?
No. Those changes just fix and extend the syntax of arithmetic
expressions within WHERE clauses.
Is this still true ? One clear need was the possibility of including
expressions in the update statement.
More information about the grass-dev