Another option would be to do this in the DB Manager - ie use the SQLite
engine directly, but you would have to recouch your Field Calculator
expression as SQL.
Andy
On 01/03/2017 22:33, Randal Hale wrote:
Attribute! Used Field Calculator to split an attribute to get the
zipcode into a standa
On 2 March 2017 at 08:33, Randal Hale wrote:
> Attribute! Used Field Calculator to split an attribute to get the zipcode
> into a standalone column. I then hit save and watched the fun.
Can you try doing this outside of the attribute table? Ie just click
the main window field calculator toolbar b
Just out of curiosity:
Maybe you could try it once with sqlite instead of SpaliaLite and see if
there is a difference (If you have some spare 20 minutes ;) ). So you
could maybe sort out if its really a SpatiaLite problem or that general
OGR problem Nyall pointed to.
Cheers
Bernd
Am 01.03
Attribute! Used Field Calculator to split an attribute to get the
zipcode into a standalone column. I then hit save and watched the fun.
And yes that seems to be it. Good, I'm not crazy (on this issue).
Randy
On 03/01/2017 05:23 PM, Nyall Dawson wrote:
On 2 March 2017 at 08:08, Randal Hale
On 2 March 2017 at 08:08, Randal Hale wrote:
> I'm using 2.18.4
>
> I'm working with Address point data. My typical process is to import the
> data into PostGIS/Postgresql and work with it. I decided to work with
> spatialite and do some data cleanup.
>
> I have 222519 points. I made a change to a
I'm using 2.18.4
I'm working with Address point data. My typical process is to import the
data into PostGIS/Postgresql and work with it. I decided to work with
spatialite and do some data cleanup.
I have 222519 points. I made a change to all of them and hit save. So
for the next 20 minutes I
