https://issues.qgis.org/https://issues.qgis.org/favicon.ico2013-11-07T09:21:37ZQGIS Issue TrackingQGIS Application - Bug report #9029: Spatialite Integer columns cannot be usedhttps://issues.qgis.org/issues/9029?journal_id=462202013-11-07T09:21:37ZBrian Freedbfreed@stineconsulting.com
<ul></ul><p>One exception: integer primary key still writes</p> QGIS Application - Bug report #9029: Spatialite Integer columns cannot be usedhttps://issues.qgis.org/issues/9029?journal_id=462212013-11-07T09:28:24ZJürgen Fischerjef@norbit.de
<ul></ul><p>Hm, I don't really understand. You're digitizing on a layer with NULL contraints, you aren't entering non-NULL values and cannot save? Isn't that what ought to happen?</p> QGIS Application - Bug report #9029: Spatialite Integer columns cannot be usedhttps://issues.qgis.org/issues/9029?journal_id=462222013-11-07T09:34:53ZBrian Freedbfreed@stineconsulting.com
<ul></ul><p>No, sorry, I wasn't clear. I have a layer I use for making Atlas Coverages. It's got not nulls and various triggers to force snapping to the correct page size. I've been working backwards for why it's always worked great in 1.8 but doesn't in 2.<br />So along the way I've tried lots of things.</p>
<p>But in the end:<br />Create a new spatialite layer. Define some columns as "whole number". That's it - no not nulls, no triggers, just a basic layer.<br />Now digitize something, and populate all the columns. Save the edits.<br />Look at the feature: all the integer columns are NULL (despite having entered some number in the form).</p>
<p>I probably shouldn't have clouded the issue by mentioning the not null. Entering all my data, then having Spatialite bomb with a "page_num cannot be null" error, even though I gave it a page_num was just one of the steps along the way. :-)</p> QGIS Application - Bug report #9029: Spatialite Integer columns cannot be usedhttps://issues.qgis.org/issues/9029?journal_id=462232013-11-07T10:12:19ZBrian Freedbfreed@stineconsulting.com
<ul></ul><p>I just uninstalled the 64-bit version and downloaded the 32-bit installer. It doesn't seem to have the same problem.</p>
<p>I should have specified 64-bit in platform, I guess. It appears to be a 64-bit only bug.</p> QGIS Application - Bug report #9029: Spatialite Integer columns cannot be usedhttps://issues.qgis.org/issues/9029?journal_id=462522013-11-11T00:04:55ZMatthias Kuhn
<ul></ul><p>Some fixes have been applied to the spatialite provider (also affecting "whole number" type) between 2.0 and master.<br />It would be great if it would be possible to check if this is fixed in master.</p> QGIS Application - Bug report #9029: Spatialite Integer columns cannot be usedhttps://issues.qgis.org/issues/9029?journal_id=462612013-11-11T07:49:01ZBrian Freedbfreed@stineconsulting.com
<ul></ul><p>I re-ran the OSGeo4W 64-bit installer for qgis-dev, and in build 5f5cd4c, Spatialite layers are working fine. <br />Thanks for the heads up!</p> QGIS Application - Bug report #9029: Spatialite Integer columns cannot be usedhttps://issues.qgis.org/issues/9029?journal_id=462622013-11-11T07:54:03ZBrian Freedbfreed@stineconsulting.com
<ul></ul><p>Although, it seems like Spatialite version 3 databases don't have editable views either now. <br />(I'll update the other bug report; previously only version 4 databases had that problem)</p> QGIS Application - Bug report #9029: Spatialite Integer columns cannot be usedhttps://issues.qgis.org/issues/9029?journal_id=462912013-11-12T06:46:28ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Resolution</strong> set to <i>fixed/implemented</i></li><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul>