Re: [sqlite] Bug in sqlite3.c

I tried "INSERT INTO ft(ft) VALUES('integrity-check')" and it also did not give any error. But the rebuild command helped solve my problem as the crashes stopped, otherwise my application was crashing at every commit operation (thanks a lot for that). Is there any command/API which can bypass

Re: [sqlite] Bug in sqlite3.c

On 4/6/62 12:11, bhandari_nikhil wrote: Thanks Dan. I had checked the database integrity using the following command: sqlite3 myfile.db "PRAGMA integrity_check;" Try "INSERT INTO ft(ft) VALUES('integrity-check')", where "ft" is the name of the fts5 table. And it had reported ok. I will

Re: [sqlite] Bug in sqlite3.c

Thanks Dan. I had checked the database integrity using the following command: sqlite3 myfile.db "PRAGMA integrity_check;" And it had reported ok. I will see if I can share the database file here. Can you let me know how to check the db file (in case I am not able to share the db file here) ? And

Re: [sqlite] Bug in sqlite3.c

On 3/6/62 12:51, bhandari_nikhil wrote: I am facing a crash in sqlite3fts5BufferAppendBlob. Following is the backtrace: #0 sqlite3Fts5BufferAppendBlob (pRc=pRc@entry=0xf54139c8, pBuf=pBuf@entry=0xf5afeb90, nData=4294967295, pData=0xf49fff76 "90246ture") at sqlite3.c:180474 #1 0xf717b6f8

[sqlite] Bug in sqlite3.c

I am facing a crash in sqlite3fts5BufferAppendBlob. Following is the backtrace: #0 sqlite3Fts5BufferAppendBlob (pRc=pRc@entry=0xf54139c8, pBuf=pBuf@entry=0xf5afeb90, nData=4294967295, pData=0xf49fff76 "90246ture") at sqlite3.c:180474 #1 0xf717b6f8 in fts5WriteAppendTerm

Re: [sqlite] bug in sqlite3??

Let's not forget that the size of the database is going to grow above and beyond the "number of rows" due to pages that aren't reserved for your data, such index pages, etc. On Tue, May 28, 2019 at 1:49 PM Jens Alfke wrote: > > > > On May 26, 2019, at 7:21 PM, John Brigham wrote: > > > > The

Re: [sqlite] bug in sqlite3??

On 28 May 2019, at 6:49pm, Jens Alfke wrote: > Try opening a copy of the database with the `sqlite3` CLI tool and entering > “PRAGMA vacuum;”. Then exit and look at the file size. Alternatively use the sqlite3_analyze tool and read the "Pages on the freelist" figures.

Re: [sqlite] bug in sqlite3??

> On May 26, 2019, at 7:21 PM, John Brigham wrote: > > The size of the file reflects the number of rows that should be present. And > furthermore, the size of the file nicely reflects the number of days. […] > Trust me when I say that this file is way to big for the number of rows. SQLite

Re: [sqlite] bug in sqlite3??

On 5/26/19, John Brigham wrote: > I have an Arduino/Python experiment that generates lots of simple > numerical data; about 7000 records a day. I run it through Python into an > sqlite3 database.I have been running this for 8 months. I start a new > database about every six weeks so every

[sqlite] bug in sqlite3??

I have an Arduino/Python experiment that generates lots of simple numerical data; about 7000 records a day. I run it through Python into an sqlite3 database.I have been running this for 8 months. I start a new database about every six weeks so every database has about 260k rows. I have

Re: [sqlite] Bug in sqlite3 (CLI, linux/Ubuntu)

act that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. >-Original Message- >From: sqlite-users [mailto:sqlite-users- >boun...@mailinglists.sqlite.org] On Behalf Of >softw...@quantentunnel.de >Sent: Saturday, 30 March, 20

Re: [sqlite] Bug in sqlite3 (CLI, linux/Ubuntu)

> Dear colleagues > > I detected an unexpected behaviour in sqlite3 (CLI) that I consider a bug as > it seems not documented. > > When using an init file (even if an empty file), sqlite3 outputs an extra > empty line to stdout. This messes up parsing of the sqlite3 output, as this > line

Re: [sqlite] Bug in sqlite3 (CLI, linux/Ubuntu)

On 30-3-2019 12:28, softw...@quantentunnel.de wrote: Dear colleagues I detected an unexpected behaviour in sqlite3 (CLI) that I consider a bug as it seems not documented. When using an init file (even if an empty file), sqlite3 outputs an extra empty line to stdout. This messes up parsing

[sqlite] Bug in sqlite3 (CLI, linux/Ubuntu)

Dear colleagues I detected an unexpected behaviour in sqlite3 (CLI) that I consider a bug as it seems not documented. When using an init file (even if an empty file), sqlite3 outputs an extra empty line to stdout. This messes up parsing of the sqlite3 output, as this line is not present in

Re: [sqlite] Bug in sqlite3.exe?

SQLite Database > Subject: Re: [sqlite] Bug in sqlite3.exe? > > On Tue, Sep 24, 2013 at 12:35 PM, Staffan Tylen > <staffan.ty...@gmail.com>wrote: > > > SQLite version 3.7.16.2 2013-04-12 11:52:43 > > Enter ".help" for instructions > > Enter S

Re: [sqlite] Bug in sqlite3.exe?

On 9/24/2013 12:49 PM, John Drescher wrote: On Tue, Sep 24, 2013 at 12:35 PM, Staffan Tylen wrote: SQLite version 3.7.16.2 2013-04-12 11:52:43 Enter ".help" for instructions Enter SQL statements terminated with a ";" sqlite> .tables CityCountry

Re: [sqlite] Bug in sqlite3.exe?

Many who solved this, thank you all. Staffan On Tue, Sep 24, 2013 at 7:11 PM, Yuriy Kaminskiy wrote: > Staffan Tylen wrote: > > On Tue, Sep 24, 2013 at 6:50 PM, Simon Slavin > wrote: > > > >> On 24 Sep 2013, at 5:35pm, Staffan Tylen

Re: [sqlite] Bug in sqlite3.exe?

Staffan Tylen wrote: > On Tue, Sep 24, 2013 at 6:50 PM, Simon Slavin wrote: > >> On 24 Sep 2013, at 5:35pm, Staffan Tylen wrote: >> >>> sqlite> .tables >>> CityCountry Languages >>> Country Country

Re: [sqlite] Bug in sqlite3.exe?

On 09/24/2013 11:53 PM, Staffan Tylen wrote: Well, it's not my database I'm looking at. What puzzles me is that Country Languages works but Country Official Languages doesn't, so could there be a parsing problem? It's because the AS keyword is optional. These two are equivalent: SELECT

Re: [sqlite] Bug in sqlite3.exe?

On Tue, Sep 24, 2013 at 12:53 PM, Staffan Tylen wrote: > Well, it's not my database I'm looking at. What puzzles me is that Country > Languages works but Country Official Languages doesn't, so could there be a > parsing problem? > > I think I see what is happening.. when

Re: [sqlite] Bug in sqlite3.exe?

On Tue, Sep 24, 2013 at 12:35 PM, Staffan Tylen wrote: > SQLite version 3.7.16.2 2013-04-12 11:52:43 > Enter ".help" for instructions > Enter SQL statements terminated with a ";" > sqlite> .tables > CityCountry Languages > Country

Re: [sqlite] Bug in sqlite3.exe?

Well, it's not my database I'm looking at. What puzzles me is that Country Languages works but Country Official Languages doesn't, so could there be a parsing problem? I agree, the names should be quoted ... On Tue, Sep 24, 2013 at 6:50 PM, Simon Slavin wrote: > > On 24

Re: [sqlite] Bug in sqlite3.exe?

On Tue, Sep 24, 2013 at 12:35 PM, Staffan Tylen wrote: > SQLite version 3.7.16.2 2013-04-12 11:52:43 > Enter ".help" for instructions > Enter SQL statements terminated with a ";" > sqlite> .tables > CityCountry Languages > Country

Re: [sqlite] Bug in sqlite3.exe?

On 24 Sep 2013, at 5:35pm, Staffan Tylen wrote: > sqlite> .tables > CityCountry Languages > Country Country Official Languages > Country CapitalsCountryLanguage Either don't use spaces in your token names (table

Re: [sqlite] Bug in sqlite3.exe?

On Tue, Sep 24, 2013 at 12:35 PM, Staffan Tylen wrote: > SQLite version 3.7.16.2 2013-04-12 11:52:43 > Enter ".help" for instructions > Enter SQL statements terminated with a ";" > sqlite> .tables > CityCountry Languages > Country

[sqlite] Bug in sqlite3.exe?

SQLite version 3.7.16.2 2013-04-12 11:52:43 Enter ".help" for instructions Enter SQL statements terminated with a ";" sqlite> .tables CityCountry Languages Country Country Official Languages Country CapitalsCountryLanguage sqlite> select

[sqlite] Bug? Shell (sqlite3.exe) exits after ".read"-ing a file that contains two errors

Hello List! I see unexpected behavior using sqlite3's .read command. The basic problem is illustrated by the following test file: C:\>type test2.sql -- two errors, sqlite3 exits select count(*) from no_table_a; select count(*) from no_table_b; C:\> Here's the result of running

Re: [sqlite] BUG: The sqlite3 shell does not call setlocale

On 12/14/09 16:56 , "Jay A. Kreibich" wrote: > On Mon, Dec 14, 2009 at 10:41:04AM +0100, Jean-Denis Muys scratched on the > wall: >> >> So Jay, what you are saying is that SQLite doesn't have to provide bug-free >> features when those features are optional? > [snip] > So,

Re: [sqlite] BUG: The sqlite3 shell does not call setlocale

On Sat, Dec 12, 2009 at 12:39:23PM -0800, Roger Binns wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Alexey Pechnikov wrote: > > On unix the shell must do this initialisation: > > > > setlocale(LC_ALL, ""); > > Why? Yes I know what the call does, but what desirable effect does it

Re: [sqlite] BUG: The sqlite3 shell does not call setlocale

On Mon, Dec 14, 2009 at 10:41:04AM +0100, Jean-Denis Muys scratched on the wall: > > On 12/13/09 16:34 , "Jay A. Kreibich" wrote: > > > On Sun, Dec 13, 2009 at 01:47:43PM +0300, Alexey Pechnikov scratched on the > > wall: > > >> On Sunday 13 December 2009 02:09:48 Roger Binns

Re: [sqlite] BUG: The sqlite3 shell does not call setlocale

On 12/13/09 16:34 , "Jay A. Kreibich" wrote: > On Sun, Dec 13, 2009 at 01:47:43PM +0300, Alexey Pechnikov scratched on the > wall: >> On Sunday 13 December 2009 02:09:48 Roger Binns wrote: >> The libsqlite is locale-independent but sqlite3 shell linked with >> readline and

Re: [sqlite] BUG: The sqlite3 shell does not call setlocale

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexey Pechnikov wrote: > The locale of CSV file may be defined in virtualtable arguments like to > create virtual table test using VirtualText > ('/srv/projects/work/billing/export/ats.csv','utf8','','.',',',','); > > But _default_ may be system

Re: [sqlite] BUG: The sqlite3 shell does not call setlocale

On Sun, Dec 13, 2009 at 01:47:43PM +0300, Alexey Pechnikov scratched on the wall: > Hello! > > On Sunday 13 December 2009 02:09:48 Roger Binns wrote: > > Alexey Pechnikov wrote: > > > This is standart for all i18n applications. > > > > The SQLite shell is not an i18n application, and this is

Re: [sqlite] BUG: The sqlite3 shell does not call setlocale

Hello! On Sunday 13 December 2009 02:09:48 Roger Binns wrote: > Alexey Pechnikov wrote: > > This is standart for all i18n applications. > > The SQLite shell is not an i18n application, and this is deliberate. It is > a developer tool. That is why for example it always uses a dot for a >

Re: [sqlite] BUG: The sqlite3 shell does not call setlocale

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexey Pechnikov wrote: > This is standart for all i18n applications. The SQLite shell is not an i18n application, and this is deliberate. It is a developer tool. That is why for example it always uses a dot for a decimal point and not a comma

Re: [sqlite] BUG: The sqlite3 shell does not call setlocale

Hello! On Saturday 12 December 2009 23:39:23 Roger Binns wrote: > > setlocale(LC_ALL, ""); > > Why? Yes I know what the call does, but what desirable effect does it have > on shell input and output? Pretty much all formatted output is done using > %s. The only float output is for timing

Re: [sqlite] BUG: The sqlite3 shell does not call setlocale

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexey Pechnikov wrote: > On unix the shell must do this initialisation: > > setlocale(LC_ALL, ""); Why? Yes I know what the call does, but what desirable effect does it have on shell input and output? Pretty much all formatted output is done

[sqlite] BUG: The sqlite3 shell does not call setlocale

Hello! On unix the shell must do this initialisation: setlocale(LC_ALL, ""); Best regards, Alexey Pechnikov. http://pechnikov.tel/ ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] BUG: Tcl sqlite3 command line options (-vfs option)

Hi, I just noticed by code review small and easy to fix bug in -vfs option handling code. sqlite3 Tcl command line syntax is following: sqlite3 HANDLE ?FILENAME ?-vfs VFSNAME? ?-readonly BOOLEAN? ?-create BOOLEAN? ?-nomutex BOOLEAN? ?-fullmutex BOOLEAN? But if -vfs option is in the middle, the

[sqlite] Bug in Sqlite3 and parameters

I am using a parametric sql statement, with parameters of the form :Name The following routines give an access violation, when called via the windows dll: sqlite3_bind_parameter_name sqlite3_bind_parameter_index The access violation indicates that a NULL pointer is being accessed. A brief look