Re: [sqlite] Strange behavior on SQLite 3.7x compared with 3.6.22

Tested on Windows XP with the binary download from SQlite's website (http://www.sqlite.org/sqlite-shell-win32-x86-3070900.zip ) and the problem occurred. See image below: On 08/12/2011, at 16:23, Black, Michael (IS) wrote: I tested 3.7.9 on both Windows and Linux. Both gave just "31|"

Re: [sqlite] Strange behavior on SQLite 3.7x compared with 3.6.22

I tested 3.7.9 on both Windows and Linux. Both gave just "31|" as the output instead of "31|0" as you show. And changing the select 9 made no difference...still got the same "31|" answer for both. I'm compiling with default options. Michael D. Black Senior Scientist Advanced

Re: [sqlite] Strange behavior on SQLite 3.7x compared with 3.6.22

Here it goes. A more simplified version: -- -- Table updated by the trigger TGR_InventoryControl_AfterInsert -- CREATE TABLE InventoryControl ( InventoryControlId INTEGER PRIMARY KEY AUTOINCREMENT, SKU INTEGER NOT NULL, Variant INTEGER NOT NULL DEFAULT 0, ControlDate DATE NOT NULL,

Re: [sqlite] Strange behavior on SQLite 3.7x compared with 3.6.22

Your test_case.sql didn't come thru. Can you report it in-ilne with an email? Michael D. Black Senior Scientist Advanced Analytics Directorate Advanced GEOINT Solutions Operating Unit Northrop Grumman Information Systems From:

Re: [sqlite] Command line option equivalent for .read

On 8 December 2011 17:05, David Walker wrote: > Hi, > > Having played around with a shell script that calls SQLite I have noticed > that I can something like > >        .separator STRING      at the SQLite prompt >        .mode line > > or I can do > >        sqlite3

[sqlite] Strange behavior on SQLite 3.7x compared with 3.6.22

Hi, We've being working with SQLite version 3.6.22 in our project and we wish to upgrade it to the latest one. During the tests with the new library version, we noticed a strange behavior related to a trigger which updates the last inserted row. We where able to simplify the data model

[sqlite] Command line option equivalent for .read

Hi, Having played around with a shell script that calls SQLite I have noticed that I can something like .separator STRING at the SQLite prompt .mode line or I can do sqlite3 -separator STRING at the command line sqlite3 - line This is both useful and

Re: [sqlite] SqLite Index corruption issue

On Wed, Dec 7, 2011 at 10:05 AM, Rangwala, Alefiya (GE Energy) < alefiya.rangw...@ge.com> wrote: > Hi, > > I wanted to know in what situations does the Sqlite db indexes can get > corrupted. > http://www.sqlite.org/howtocorrupt.html > > I am using a sqlite db version 3. I faced an issue, that

[sqlite] SqLite Index corruption issue

Hi, I wanted to know in what situations does the Sqlite db indexes can get corrupted. I am using a sqlite db version 3. I faced an issue, that my indexes got corrupted and the select queries to the db returned an invalid result set. The moment I deleted the indexes, it returned a valid result