[sqlite] sqlite bug report

Summary Alter table rename to fails if the database contains a view which selects from a nonexistent table. Seen on sqlite 3.27.2. Script to reproduce it: create view view_1 as select * from table_1; create table table_2 (col_1 text, col_2 text); alter table table_2 rename to table_3; The

Re: [sqlite] SQLite bug: Malformed UTF16 leads to a 2-byte buffer overread

On 9/29/18, Kelvin Jiang wrote: > Hi there, > > I'm using SQlite 3.12.1 on Android device and we found this bug on most > Android devices. Maybe this is a bug in Android or in the SQLite interface that are built into Android. But SQLite itself seems to be working correct. Or, at least, I am

[sqlite] SQLite bug: Malformed UTF16 leads to a 2-byte buffer overread

Hi there, I'm using SQlite 3.12.1 on Android device and we found this bug on most Android devices. The problem can be reproduced by following procedures: 1. Prepare a malformed Java String, like "123", then cut it right from the middle of the surrogates, like "123".substring(0, 4), and append

Re: [sqlite] sqlite bug? .mode insert does not quote identifiers

On 4/6/18, jon baldry wrote: > I have identifiers that unfortunately have a hyphen within them. > > I want to output the data from the tables with those identifiers using > .mode insert and .out foo.sql for re-loading. > > I have worked around this in PHP to modify the output,

[sqlite] sqlite bug? .mode insert does not quote identifiers

I have identifiers that unfortunately have a hyphen within them. I want to output the data from the tables with those identifiers using .mode insert and .out foo.sql for re-loading. I can't use .dump easily as i want to modify the tables before re-loading the data, so .mode insert seemed my

Re: [sqlite] SQLITE bug

On 2017/09/03 4:16 PM, Joseph L. Casale wrote: -Original Message- From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of R Smith Sent: Sunday, September 3, 2017 7:51 AM To: sqlite-users@mailinglists.sqlite.org Subject: Re: [sqlite] SQLITE bug Lastly

Re: [sqlite] SQLITE bug

On 9/3/17 10:16 AM, Joseph L. Casale wrote: -Original Message- From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of R Smith Sent: Sunday, September 3, 2017 7:51 AM To: sqlite-users@mailinglists.sqlite.org Subject: Re: [sqlite] SQLITE bug Lastly

Re: [sqlite] SQLITE bug

-Original Message- From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of R Smith Sent: Sunday, September 3, 2017 7:51 AM To: sqlite-users@mailinglists.sqlite.org Subject: Re: [sqlite] SQLITE bug > Lastly, a comment I've made possibly more than o

Re: [sqlite] SQLITE bug

I think this has been answered already in that it is not a bug, but I would like to mention why it works the way it works. Imagine you have some tables, like a list of clients (table: client) and a list of contacts which are foreign-keyed (or simply used in conjunction) with the client parent

Re: [sqlite] SQLITE bug

On 8/31/17, Noah Simon wrote: > Hello, > While using the sqlite3 SQL shell from macOS Sierra Terminal, a bug (I > think) occurred. > > Version number: > sqlite> .version > SQLite 3.13.0 2016-05-18 10:57:30 fc49f556e48970561d7ab6a2f24fdd7d9eb81ff2 > > What happened was I

[sqlite] SQLITE bug

Hello, While using the sqlite3 SQL shell from macOS Sierra Terminal, a bug (I think) occurred. Version number: sqlite> .version SQLite 3.13.0 2016-05-18 10:57:30 fc49f556e48970561d7ab6a2f24fdd7d9eb81ff2 What happened was I created a table with an autoincremented primary key. After creating a

Re: [sqlite] SQLite Bug Disclosure

Thank you, Dr. Hipp! On Sun, Jan 22, 2017 at 9:40 AM, Richard Hipp wrote: > Thanks for sending the bug report, Ian. Unfortuantely, the repro > script did not work for me. I think you sent the wrong file. > Nevertheless, I was able to track down and fix the problem based on >

Re: [sqlite] SQLite Bug Disclosure

Thanks for sending the bug report, Ian. Unfortuantely, the repro script did not work for me. I think you sent the wrong file. Nevertheless, I was able to track down and fix the problem based on your description. A fix is on trunk. To the rest of the world: the problem was in the command-line

Re: [sqlite] SQLite Bug Disclosure

This mailing list strips all attachments. Please forward the attachments directly to me at d...@sqlite.org On 1/21/17, ian wrote: > To Whom it may Concern: > > While performing some work with SQLite3, our team discovered a set of > inputs that, when passed to SQLite3, would

[sqlite] SQLite Bug Disclosure

To Whom it may Concern: While performing some work with SQLite3, our team discovered a set of inputs that, when passed to SQLite3, would trigger a segmentation fault. I have attached both a write up of our findings while investigating the fault (SQLite3 Writeup.docx), and a minimized version of

[sqlite] sqlite bug report

Bug report I downloaded sqlite 3.10.0 released in 2016-1-6, earlier I downloaded sqlite 3.9.2 and earlier version. I found below 2 bugs: bug1: Database directory which contains Simplified Chinese Character not support. bug2: Simplified Chinese Character in database table display error. bug1:

Re: [sqlite] sqlite bug report

On Thu, Nov 13, 2014 at 4:41 PM, Hinrichsen, John wrote: > In this example, bad data is returned. There is no assert. valgrind does > not complain either. > It asserts if you recompile with -DSQLITE_DEBUG > > Is there an ETA on when 3.8.7.2 will be released? > Next

Re: [sqlite] sqlite bug report

In this example, bad data is returned. There is no assert. valgrind does not complain either. Is there an ETA on when 3.8.7.2 will be released? On Thu, Nov 13, 2014 at 1:12 PM, Richard Hipp wrote: > This is https://www.sqlite.org/src/info/094d39a4c95ee4 which has been >

Re: [sqlite] sqlite bug report

This is https://www.sqlite.org/src/info/094d39a4c95ee4 which has been fixed in trunk and will be fixed in 3.8.7.2. On Thu, Nov 13, 2014 at 1:05 PM, Hinrichsen, John wrote: > The following SQL produces an incorrect result with sqlite-3.8.7.1: > > CREATE TABLE A( > symbol

[sqlite] sqlite bug report

The following SQL produces an incorrect result with sqlite-3.8.7.1: CREATE TABLE A( symbol TEXT, type TEXT ); INSERT INTO A VALUES('ABCDEFG','chars'); INSERT INTO A VALUES('1234567890','num'); CREATE TABLE B( chars TEXT, num TEXT ); CREATE TABLE IF NOT EXISTS C AS SELECT A.symbol AS

Re: [sqlite] sqlite bug after CREATE UNIQUE INDEX

I think the point is that attempting to create the unique index should fail (with an error) and the index not be created rather than creating a unique index with duplicates (or whatever it is doing) causing subsequent queries to return incorrect results. >On Wed, 30 Jul 2014 09:10:29 +0400

Re: [sqlite] sqlite bug after CREATE UNIQUE INDEX

On Wed, 30 Jul 2014 09:10:29 +0400 Pavel Pimenov wrote: > CREATE TABLE fly_hash_block(tth_id integer PRIMARY KEY NOT NULL, tth > number NOT NULL); > INSERT INTO fly_hash_block VALUES(1,1); > INSERT INTO fly_hash_block VALUES(2,2); > INSERT INTO fly_hash_block

[sqlite] sqlite bug after CREATE UNIQUE INDEX

hi C:\!dc-db\db-sqlite-corrupt\db-uniq-bug>sqlite3 --version 3.8.5 2014-06-04 14:06:34 b1ed4f2a34ba66c29b130f8d13e9092758019212 C:\!dc-db\db-sqlite-corrupt\db-uniq-bug>sqlite3.exe FlylinkDC.sqlite 0 SQL> CREATE TABLE fly_hash_block(tth_id integer PRIMARY KEY NOT NULL, tth number NOT NULL);

Re: [sqlite] SQLite bug report: type mismatch security issue in sqlite3.c version 3.7.13

On Fri, Jul 25, 2014 at 9:50 AM, Yunjiao Xue wrote: > To whom it may concern, > > We are using SQLite 3.7.13 with an amalgamation version of sqlite3.c. We > discovered a type mismatch security issue with a recent Fortify scan. The > problem is on lines 22407, 51807,

[sqlite] SQLite bug report: type mismatch security issue in sqlite3.c version 3.7.13

To whom it may concern, We are using SQLite 3.7.13 with an amalgamation version of sqlite3.c. We discovered a type mismatch security issue with a recent Fortify scan. The problem is on lines 22407, 51807, 63005, 93150 of sqlite3.c. For example, the function strHash() in sqlite3.c is declared

[sqlite] SQLite bug: building/running SQLite on Cygwin64

For details, see below. Here is a new patch, which applies the MAX_PATH fix in os_win.c to Cygwin as well. Additional remark: This is not a bug in Cygwin64: calling win32 functions from Cygwin executables is unsupported even though it normally works fine (GetTempPath apparently is one of the

Re: [sqlite] sqlite bug? Subquery containing like-expression in where clause with starting '%' returns no rows, but without '%' does

mean, not as I say". Sent from Samsung Mobile Original message From: Petite Abeille <petite.abei...@gmail.com> Date: To: General Discussion of SQLite Database <sqlite-users@sqlite.org> Subject: Re: [sqlite] sqlite bug? Subquery containing like-expression i

Re: [sqlite] sqlite bug? Subquery containing like-expression in where clause with starting '%' returns no rows, but without '%' does

Am Sonntag, den 03.02.2013, 14:00 -0700 schrieb Keith Medcalf: > > SELECT moz_places.id, moz_places.url, moz_places.title, moz_bookmarks.parent > > FROM moz_places, moz_bookmarks > > WHERE moz_places.id = moz_bookmarks.fk > >and moz_bookmarks.parent = (select id > >

Re: [sqlite] sqlite bug? Subquery containing like-expression in where clause with starting '%' returns no rows, but without '%' does

> SELECT moz_places.id, moz_places.url, moz_places.title, moz_bookmarks.parent > FROM moz_places, moz_bookmarks > WHERE moz_places.id = moz_bookmarks.fk >and moz_bookmarks.parent = (select id > from moz_bookmarks > where

[sqlite] sqlite bug? Subquery containing like-expression in where clause with starting '%' returns no rows, but without '%' does

Could this be a bug? SELECT moz_places.id, moz_places.url, moz_places.title, moz_bookmarks.parent FROM moz_places , moz_bookmarks WHERE moz_places.id = moz_bookmarks.fkand moz_bookmarks.parent = (select id from moz_bookmarks where title like '%arbeit%') returns

Re: [sqlite] SQLite bug?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/03/12 21:01, Steinar Midtskogen wrote: > xCreate()/xConnect() will run through the argument list and do a PRAGMA > table_info(%s) and then a couple of SELECT ... FROM %s. The point I was trying to make is that this is not a generic SQLite

Re: [sqlite] SQLite bug?

Roger Binns writes: > On 07/03/12 13:46, Steinar Midtskogen wrote: >> I think indeed that this is a problem: > > I cannot reproduce it using my own virtual tables. This strongly implies > that it is something to do with the code for your virtual tables. Doesn't > your

Re: [sqlite] SQLite bug?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/03/12 13:46, Steinar Midtskogen wrote: > I think indeed that this is a problem: I cannot reproduce it using my own virtual tables. This strongly implies that it is something to do with the code for your virtual tables. Doesn't your

Re: [sqlite] SQLite bug?

Steinar Midtskogen writes: > I can easily check that the argument doesn't match argv[2], but if > it's still possible to get into a loop like this if virtual tables > refer to eachother, then I don't think it's possible to detect this in > the VT code. I think indeed that

Re: [sqlite] SQLite bug?

"Jay A. Kreibich" writes: > On Wed, Mar 07, 2012 at 08:58:27PM +0100, Steinar Midtskogen scratched on the > wall: >> I've created a module which will take a table as an argument. In >> Xconnect it will run a query on that table. Then I accidently used >> the name of the

Re: [sqlite] SQLite bug?

On Wed, Mar 07, 2012 at 08:58:27PM +0100, Steinar Midtskogen scratched on the wall: > I've created a module which will take a table as an argument. In > Xconnect it will run a query on that table. Then I accidently used > the name of the virtual table in the argument list: > > CREATE VIRTUAL

[sqlite] SQLite bug?

I've created a module which will take a table as an argument. In Xconnect it will run a query on that table. Then I accidently used the name of the virtual table in the argument list: CREATE VIRTUAL TABLE v USING my_module(v); which seems to have triggered an infinite call loop. I suppose

Re: [sqlite] Sqlite Bug Report!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > When I compile sqlite3 in VC++6.0, it does not work, but in VS2010 it > can work. http://www.beiww.com/doc/oss/smart-questions.html Roger -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux)

[sqlite] Sqlite Bug Report!

Hello. (I am Chinese, not good at English. ^_^) When I compile sqlite3 in VC++6.0, it does not work, but in VS2010 it can work. It report a runtime errro. My code as following. #include #include #include #include #include "sqlite3.h" #include #include int main() { char db[] = "db.db";

Re: [sqlite] sqlite bug? -- inconsistent time searches

Ian Strascina wrote: > So is this a sqlite bug in that inconsistent results are coming from queries > that should be functionally equivalent according to the above documentation Realize that SQLite doesn't have a date or datetime data types. All the calculations are

Re: [sqlite] sqlite bug? -- inconsistent time searches

>It's a pain in the arse that one has to pay for copies of the >ISOs. What do they think we're paying them for ? I also find this a perverse effect totally contrary to their mission or at least its spirit: produce good standards for public use. Without free access to reference up-to-date

Re: [sqlite] sqlite bug? -- inconsistent time searches

On 2 Apr 2011, at 4:30pm, Simon Slavin wrote: > The ISO standard separates date and time with exactly 'T' or 't'. Wrong. Sorry about that. The ISO standard specifies a capital 'T'. Other standards which are obviously based on it suggest that a lower-case 't' is acceptable. Apologies for

Re: [sqlite] sqlite bug? -- inconsistent time searches

On 1 Apr 2011, at 11:31pm, Ian Strascina wrote: > I have come across inconsistent results of queries using datetime functions > and > values. I have based everything I tested off of this page: > http://www.sqlite.org/lang_datefunc.html There's a problem with that web page. The ISO standard

[sqlite] sqlite bug? -- inconsistent time searches

I have come across inconsistent results of queries using datetime functions and values. I have based everything I tested off of this page: http://www.sqlite.org/lang_datefunc.html I have a table with a /start_date/ property. The values written are UTC time of the format

[sqlite] SQLite bug

Sorry, but all 3.7.x versions, compiled usind OpenWatcom for OS/2, can not create database file. For example, when I run * shell test.sqlite * where test.sqlite is absent, and try to create table, say, *create table a (b int);* I got message *Error disk I/O* Can you help me to solve this

[sqlite] SQLite bug report: Bad truncation in column mode with non ASCII characters

In ".mode column", the function used to compute the length of the string to print does not account for multi-byte characters, resulting in a shorter string, and all remaining fields in the line shifted to the left. Example: sqlite> select * from test limit 3; namename2 name3

Re: [sqlite] sqlite bug with collating sequences?

On Mar 29, 2010, at 10:40 AM, Jay A. Kreibich wrote: > On Mon, Mar 29, 2010 at 12:16:57PM +0200, Rickard Utgren scratched > on the wall: >> On Mon, Mar 29, 2010 at 12:07, Dan Kennedy >> wrote: >> >>> This database was created with a different version of the collation

Re: [sqlite] sqlite bug with collating sequences?

On Mon, Mar 29, 2010 at 12:16:57PM +0200, Rickard Utgren scratched on the wall: > On Mon, Mar 29, 2010 at 12:07, Dan Kennedy wrote: > > > This database was created with a different version of the collation > > sequence than found in the script. I think the -nocase switch

Re: [sqlite] sqlite bug with collating sequences?

On Mon, Mar 29, 2010 at 12:07, Dan Kennedy wrote: > This database was created with a different version of the collation > sequence than found in the script. I think the -nocase switch was > probably passed to [string compare]. You are correct, it was creates with this

Re: [sqlite] sqlite bug with collating sequences?

On Mar 29, 2010, at 4:55 PM, Rickard Utgren wrote: > I've managed to break a database, and I think it's related to defining > new text collating sequences in Tcl. If I run "VACUUM" on it, it works > fine again. I was told that this would likely be a bug in SQLite. This database was created with

[sqlite] sqlite bug with collating sequences?

I've managed to break a database, and I think it's related to defining new text collating sequences in Tcl. If I run "VACUUM" on it, it works fine again. I was told that this would likely be a bug in SQLite. I've created a tarball with my broken database, and a small Tcl script that showcases the

Re: [sqlite] SQLite bug ticket - build fails on sun4-solaris-64int 2.10

to the list so I'm forwarding a compilation of them for the latter's benefit. -- Darren Duncan 1 of 2: Original Message Subject: Re: [DBD-SQLite] Re: [sqlite] SQLite bug ticket - build fails on sun4-solaris-64int 2.10 Date: Sun, 3 Jan 2010 14:55:39 +1100 From: Adam Kennedy

Re: [sqlite] SQLite bug ticket - build fails on sun4-solaris-64int 2.10

Darren Duncan wrote: > I would like to bring an apparent SQLite bug to the attention of the SQLite > core > developers as a ticket, where build fails on sun4-solaris-64int 2.10. > > This problem was reported to the DBD::SQLite (Perl binding) developers as an > automatically generated smoke

Re: [sqlite] SQLite bug ticket - build fails on sun4-solaris-64int 2.10

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Darren Duncan wrote: > Roger, thank you for this quick response, and for your tips. So from the > looks > of what you're saying, the problem is actually related to something that the > DBD::SQLite build process is doing inadequately, so now I

Re: [sqlite] SQLite bug ticket - build fails on sun4-solaris-64int 2.10

Op 2-jan-2010, om 9:32 heeft Roger Binns het volgende geschreven: > Darren Duncan wrote: >> I would like to bring an apparent SQLite bug to the attention of >> the SQLite core >> developers as a ticket, where build fails on sun4-solaris-64int 2.10 > > You'll find this is not a bug in SQLite. >

Re: [sqlite] SQLite bug ticket - build fails on sun4-solaris-64int 2.10

Roger, thank you for this quick response, and for your tips. So from the looks of what you're saying, the problem is actually related to something that the DBD::SQLite build process is doing inadequately, so now I suspect the ball will go back there to be dealt with. Thank you. -- Darren

Re: [sqlite] SQLite bug ticket - build fails on sun4-solaris-64int 2.10

Darren Duncan wrote: > I would like to bring an apparent SQLite bug to the attention of the SQLite > core > developers as a ticket, where build fails on sun4-solaris-64int 2.10 You'll find this is not a bug in SQLite. > cc: Fatal error in /opt/sunstudio12.1/prod/bin/cg > cc: Status 139 > ***

[sqlite] SQLite bug ticket - build fails on sun4-solaris-64int 2.10

I would like to bring an apparent SQLite bug to the attention of the SQLite core developers as a ticket, where build fails on sun4-solaris-64int 2.10. This problem was reported to the DBD::SQLite (Perl binding) developers as an automatically generated smoke tester ticket which can be seen here

Re: [sqlite] SQLite bug report - large databases only - 'database or disk is full'

- From: Filip Navara <filip.nav...@gmail.com> To: General Discussion of SQLite Database <sqlite-users@sqlite.org> Sent: Thu, Dec 10, 2009 1:35 am Subject: Re: [sqlite] SQLite bug report - large databases only - 'database or disk is full' On Mon, Dec 7, 2009 at 10:21 PM, <p...@

Re: [sqlite] SQLite bug report - large databases only - 'database or disk is full'

On Mon, Dec 7, 2009 at 10:21 PM, wrote: > > SQLite bug report > > Summary: > -- > > error message: > >       Error: near line 2: database or disk is full > > It happens with plenty of disk space available and with 'unlimited' database > size. > It does not happen on

Re: [sqlite] SQLite bug report - large databases only - 'database or disk is full'

On Mon, Dec 7, 2009 at 10:21 PM, wrote: > > SQLite bug report > > Summary: > -- > > error message: > >       Error: near line 2: database or disk is full > > It happens with plenty of disk space available and with 'unlimited' database > size. > It does not happen on

[sqlite] SQLite bug report - large databases only - 'database or disk is full'

SQLite bug report 　 Summary: -- error message: Error: near line 2: database or disk is full It happens with plenty of disk space available and with 'unlimited' database size. It does not happen on all systems. It does not happen on small databases. 　 Details: --

Re: [sqlite] Sqlite bug with aggregate counts query that excludes null values?

On Jul 30, 2008, at 7:14 PM, Tim Dao wrote: > I ran into strange behavior in dealing with Sqlite 3.5.9 on a 6 > million > record table I was using in development and wanted to see if I could > duplicate the error in an entirely separate instance so I tried it > from > Firefox 3.0 +

[sqlite] Sqlite bug with aggregate counts query that excludes null values?

I ran into strange behavior in dealing with Sqlite 3.5.9 on a 6 million record table I was using in development and wanted to see if I could duplicate the error in an entirely separate instance so I tried it from Firefox 3.0 + SqliteManager Plugin much to the same effect. Basically when running a

Re: [sqlite] SQLite bug on AFP?

Following up: >>> I think the solution might be as simple as compiling with - >>> DSQLITE_ENABLE_LOCKING_STYLE=1. This option only works on a Mac. >>> It enables some Apple-contributed code that does file locking that >>> works on AFP as well as on other network filesystems that the Mac

Re: [sqlite] SQLite bug on AFP?

On Jun 7, 2008, at 4:40 PM, Peter K. Stys wrote: > On Thu, Jun 5, 2008 at 2:04 PM, D. Richard Hipp <[EMAIL PROTECTED]> wrote: > >> >> On Jun 5, 2008, at 12:09 PM, Shawn Wilsher wrote: >> >>> Hey all, >>> >>> We are getting reports that sqlite is not working for users of AFP >>> (Apple Filing

Re: [sqlite] SQLite bug on AFP?

On Thu, Jun 5, 2008 at 2:04 PM, D. Richard Hipp <[EMAIL PROTECTED]> wrote: > > On Jun 5, 2008, at 12:09 PM, Shawn Wilsher wrote: > > > Hey all, > > > > We are getting reports that sqlite is not working for users of AFP > > (Apple Filing Protocol) in Bug 417037 [1]. I was wondering if this > >

Re: [sqlite] SQLite bug on AFP?

On Jun 5, 2008, at 1:32 PM, Shawn Wilsher wrote: > On Thu, Jun 5, 2008 at 4:04 PM, D. Richard Hipp <[EMAIL PROTECTED]> wrote: >> I think the solution might be as simple as compiling with - >> DSQLITE_ENABLE_LOCKING_STYLE=1. This option only works on a Mac. It >> enables some Apple-contributed

Re: [sqlite] SQLite bug on AFP?

On Thu, Jun 5, 2008 at 4:04 PM, D. Richard Hipp <[EMAIL PROTECTED]> wrote: > I think the solution might be as simple as compiling with - > DSQLITE_ENABLE_LOCKING_STYLE=1. This option only works on a Mac. It > enables some Apple-contributed code that does file locking that works > on AFP as well

Re: [sqlite] SQLite bug on AFP?

On Jun 5, 2008, at 12:09 PM, Shawn Wilsher wrote: > Hey all, > > We are getting reports that sqlite is not working for users of AFP > (Apple Filing Protocol) in Bug 417037 [1]. I was wondering if this > was a known issue, and what we could do to help get this resolved. I think the solution

Re: [sqlite] SQLite bug found by motorola

On Wed, 2005-01-26 at 14:49 -0500, D. Richard Hipp wrote: > Sibsankar constructs a database with the following schema: The previous was a private message not intended to be viewed publically, but which was sent to the public mailing list by mistake (due in part to my difficulty in adjusting to a

[sqlite] SQLite bug found by motorola

Sibsankar constructs a database with the following schema: CREATE TABLE t1(a integer primary key, b varchar collate engLish); CREATE TABLE t2(a integer primary key, b varchar); CREATE TABLE t3(a integer primary key, b varchar collate engLish); CREATE TABLE t4(a integer primary key, b varchar