Re: [sqlite] An issue with System.Data.SQLite

2017-12-22 Thread Joe Mistachkin
Aleksey Lulchenko wrote: > > Please, give me the clues what is going wrong, if you can. I think it > is a typical bug in many situations. > Could you please show us the schema of the table (or tables) involved? -- Joe Mistachkin ___ sqlite-users ma

Re: [sqlite] Suspected bug: parse error depending on platform

2017-12-22 Thread Yannick Duchêne
Ok, I see. So finally using `sqlite3.sqlite_version`, it says version 3.8.11 for the Windows version and 3.11.0 for the Ubuntu version. May be I could solve it changing the sqlite3.dll which is in the isolated Python environment. I will try to build it in the virtual machine. Thanks for having p

Re: [sqlite] sqlite3 related crash (SIGSEGV) in GNOME tracker-store

2017-12-22 Thread Paul Wise
On Fri, 2017-12-22 at 20:09 -0500, Richard Hipp wrote: > Nevertheless, we will investigate from the SQLite side, > just in case. If you need any information from the core dump, please let me know which gdb commands to run. I still have one available from the latest crash and have marked it immuta

Re: [sqlite] sqlite3 related crash (SIGSEGV) in GNOME tracker-store

2017-12-22 Thread Paul Wise
On Fri, 2017-12-22 at 20:09 -0500, Richard Hipp wrote: > There are no known issues like this with any recent version of SQLite. > Usually these kinds of things end up being heap corruption in the > application. Nevertheless, we will investigate from the SQLite side, > just in case. I see, thanks

Re: [sqlite] sqlite3 related crash (SIGSEGV) in GNOME tracker-store

2017-12-22 Thread Richard Hipp
On 12/22/17, Paul Wise wrote: > Hi all, > > I got a couple of random crashes GNOME's tracker-store daemon that > appear to be related to sqlite3. I use 3.21.0-1 from Debian buster. > > Is this a bug in sqlite3 or is it caused by data corruption? > There are no known issues like this with any rece

[sqlite] sqlite3 related crash (SIGSEGV) in GNOME tracker-store

2017-12-22 Thread Paul Wise
Hi all, I got a couple of random crashes GNOME's tracker-store daemon that appear to be related to sqlite3. I use 3.21.0-1 from Debian buster. https://bugzilla.gnome.org/show_bug.cgi?id=791243 The short backtraces are available here: https://bugzilla.gnome.org/page.cgi?id=traceparser/trace.html

Re: [sqlite] An issue with System.Data.SQLite

2017-12-22 Thread Barry
Do you allow the entity framework to create your database, or do you do it yourself? You need text affinity on the columns in question. Then any numbers will be stored as text, not numbers. See: https://sqlite.org/datatype3.html Particularly: 3.1. Determination Of Column Affinity The affinity

Re: [sqlite] Suspected bug: parse error depending on platform

2017-12-22 Thread Keith Medcalf
>The simple example below works as expected on Ubuntu, but fails on >Windows 7. Both using Python3.5 and Sqlite 2.6.0, so that’s not a >version issue. 2.6.0 is not the version of SQLite3, it is the version of the pysqlite2 wrapper module. When that third party package was incorporated into the

Re: [sqlite] Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread Radovan Antloga
Thank you Peter! I like sqlite so much and I think we all benefit if errors are fixed. I see I was not very clear with my first post. Will do better next time. Yes would be nice if people would try to understand first not just think on title text. Talking about sqlite I use it for web developmen

Re: [sqlite] Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread petern
Radovan. Thank you for sticking to your guns. Your appeal to expected behavior under other DB engines was also a very good post. I see the usual suspects of the echo chamber uselessly piled on against you to clog the forum nevertheless. That happens too frequently. BTW, here is a simpler test

[sqlite] Suspected bug: parse error depending on platform

2017-12-22 Thread Yannick Duchêne
Hello, I’em facing an issue developing a Python+SQlite3 application on Ubuntu, to be shipped on Windows 7. The simple example below works as expected on Ubuntu, but fails on Windows 7. Both using Python3.5 and Sqlite 2.6.0, so that’s not a version issue. import sqlite3 conn = sqlite3.con

Re: [sqlite] Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread Radovan Antloga
Thank you Klaus! Klaus Maas je 22.12.2017 ob 20:30 napisal: Radovan is correct. Executing the same command sequence in version 3.11.0 and 3.21.0 results in different column names for table test2. (Xubuntu 16.04 with sqlite3.11.0 and sqlite3.21.0) I marked the results with '<=' Klaus SQLi

Re: [sqlite] Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread Radovan Antloga
THANK YOU! Richard Hipp je 22.12.2017 ob 20:29 napisal: Your trouble ticket is here: https://sqlite.org/src/tktview/3b4450072511 ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listin

Re: [sqlite] Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread Klaus Maas
Radovan is correct. Executing the same command sequence in version 3.11.0 and 3.21.0 results in different column names for table test2. (Xubuntu 16.04 with sqlite3.11.0 and sqlite3.21.0) I marked the results with '<=' Klaus SQLite version 3.11.0 2016-02-15 17:29:24 Enter ".help" for usage

Re: [sqlite] Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread Richard Hipp
Your trouble ticket is here: https://sqlite.org/src/tktview/3b4450072511 -- D. Richard Hipp d...@sqlite.org ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread Radovan Antloga
Just try this sql-s: create table test(a int, b int); insert into test values (1,1); select d from (select c as d from (select a as c from test)); will return name d. create table test2 as select d from (select c as d from (select a as c from test)); will create table test2 with column name a

Re: [sqlite] Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread Radovan Antloga
What is correct? Do you understand what I write? What is my point? Tell me please. David Raymond je 22.12.2017 ob 20:04 napisal: Correct. -Original Message- From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Richard Hipp Sent: Friday, December 22, 2

Re: [sqlite] Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread Richard Hipp
On 12/22/17, Radovan Antloga wrote: > My point is you do not have to change anything regards > to how select works. SELECT statement is working just > great or OK or fine. > > CREATE TABLE AS > SELECT > > does not give same name as SELECT does. > > SELECT give name d > > CREATE TABLE AS SELEC

Re: [sqlite] Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread David Raymond
Correct. -Original Message- From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Richard Hipp Sent: Friday, December 22, 2017 1:45 PM To: SQLite mailing list Subject: Re: [sqlite] Changed behaviour or bug using field alias in 3.21.0 On 12/22/17, Radovan

[sqlite] An issue with System.Data.SQLite

2017-12-22 Thread Алексей Люльченко
Dear Sir! I would like to ask you to help me with an issue which appears while I use System.Data.SQLite database engine. I use .net framework 4.0.0, EntityFramework 6.2.0 and SQLite 1.0.106. I have an entity with properties of string type. This entity is mapped to my database table which has the

Re: [sqlite] Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread Radovan Antloga
My point is you do not have to change anything regards to how select works. SELECT statement is working just great or OK or fine. CREATE TABLE AS SELECT does not give same name as SELECT does. SELECT give name d CREATE TABLE AS SELECT create table with name a instead of d. Richard Hipp j

Re: [sqlite] Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread Richard Hipp
On 12/22/17, Radovan Antloga wrote: > In my example I have AS clause so rule 1. You did not understand my question. I think what you are asking for is that we should enhance rule 1 so that it applies even if the AS clause is contained within a subquery. -- D. Richard Hipp d...@sqlite.org __

Re: [sqlite] Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread Radovan Antloga
In my example I have AS clause so rule 1. sqlite select statement is correct or name is correct. sqlite create table as statement create table with different name that select statement return Problem is different result or name. Richard Hipp je 22.12.2017 ob 19:27 napisal: These are the rules

Re: [sqlite] Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread Richard Hipp
These are the rules that SQLite uses to name a column in the result set: (1) If there is an AS clause, use it. (2) If the result-set value comes from a table column (even indirectly, such as through a subquery, but not if the value is altered by an expression) then use the name of the column as i

Re: [sqlite] Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread Radovan Antloga
Just tried my example with PostgreSQL that have create table as statement. It work as expected. It creates table test2 with column name d. sqlite3 creates table with column name a. sqlite3 try to mimic postgresql but in this example is not. Simon Slavin je 22.12.2017 ob 17:58 napisal: On 22 D

Re: [sqlite] Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread Radovan Antloga
What? I have to write select d as d. You are not serious. You dont understand what I wrote. I get select correct but create table as does not have same name as select has. Why different result? If select gives some name I don't care what I expect create table as give me same name. Is this so ha

Re: [sqlite] Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread Radovan Antloga
Thank you very much to understand my point! This is exactly what I think. I have name and select is working ok. It gives me my name but create table as not. David Raymond je 22.12.2017 ob 17:59 napisal: I think the underlying feeling here is that if you're not doing anything tricky, and just st

Re: [sqlite] Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread David Raymond
I think the underlying feeling here is that if you're not doing anything tricky, and just straight up referencing a column name, that it should be fair to assume that the result will have that column name. I.e. with create table foo (bar); if I run select bar from foo; I should be able to assume

Re: [sqlite] Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread Simon Slavin
On 22 Dec 2017, at 4:50pm, Radovan Antloga wrote: > select d from (select c AS d from (select a AS c from test)); > > I get d as column name. If I create table with > create table as I get a as column name. As I wrote, you did not specify AS for d, so you cannot depend on a column name. If y

Re: [sqlite] Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread Radovan Antloga
Sorry but this is not related to my example. I have AS in inner select. My select return name as specified. Problem I have is with create table as where name is changed. I give example like this: select d from (select c AS d from (select a AS c from test)); I get d as column name. If I create

Re: [sqlite] journal mode and transactions

2017-12-22 Thread David Raymond
In memory databases can have rollbacks if they're using journal mode memory. The last sentence there is a little confusing... "Note that the journal_mode for an in-memory database is either MEMORY or OFF and can not be changed to a different value. An attempt to change the journal_mode of an in

Re: [sqlite] Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread Simon Slavin
On 22 Dec 2017, at 3:04pm, Tim Streater wrote: > 2) I don't see this issue mentioned when I read the PHP documentation about > their SQLite interface, nor do I see it in the Xojo docs about *their* > interface either. I assume their interfaces are not rewriting SELECT > statements to include

Re: [sqlite] What happens if an in memory database runs out of memory

2017-12-22 Thread curmudgeon
>You can run tests yourself by compiling with -DSQLITE_ENABLE_MEMSYS5 and then starting the "sqlite3.exe" command-line shell with the "--heap" argument to tell it how much memory to use. Give it a few megabytes. Then start up your in-memory database and fill it up to see what happens. Richa

[sqlite] journal mode and transactions

2017-12-22 Thread Nelson, Erik - 2
The transactions documentation (https://sqlite.org/lang_transaction.html) states >If PRAGMA journal_mode is set to OFF (thus disabling the rollback journal file) then the behavior of the ROLLBACK command is undefined. Does that correspondingly mean there's no performance benefit to wrapping

Re: [sqlite] Minor bug reports during build.

2017-12-22 Thread Michael Tiernan
On Fri, Dec 22, 2017 at 10:26 AM, Warren Young wrote: > On Dec 22, 2017, at 7:07 AM, Michael Tiernan > wrote: > > > > "Working as advertised" Okay, that's just funny. That it doesn't build is > > correct? > > It does build. Okay, it does build the binaries. Valid point. It just doesn’t inst

Re: [sqlite] TRIM Function in Python3's sqlite3 import

2017-12-22 Thread David Raymond
http://www.sqlite.org/changes.html Looks like trim was added in 10 years ago in 3.4.0 (2007-06-18) Can't help you with the Linux side of things, sorry. -Original Message- From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Ed Lipson Sent: Friday, Decemb

Re: [sqlite] Minor bug reports during build.

2017-12-22 Thread Warren Young
On Dec 22, 2017, at 7:07 AM, Michael Tiernan wrote: > > "Working as advertised" Okay, that's just funny. That it doesn't build is > correct? It does build. It just doesn’t install to a directory it can’t write to, because you told it to install system-level things. Rowan also gave you the so

Re: [sqlite] Importing Text to Create a Table

2017-12-22 Thread Peter Da Silva
I suspect you would be best advised to do more processing of the data to extract just the email addresses rather than treating it like an unstructured text blob. ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.s

[sqlite] TRIM Function in Python3's sqlite3 import

2017-12-22 Thread Ed Lipson
I shifting some Python code to Linux from Windows. I find that TRIN i smissing from the verison on Linux. Python reports this version information sqlite.version 2.6.0 for both Windows and Linux sqlite.sqlite_version 3.3.6 for Linux, 3.15.2 for Windows. Two questions: 1. When was TRIM added as a fu

Re: [sqlite] Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread Tim Streater
On 22 Dec 2017, at 09:57, Hick Gunter wrote: > The problem lies in your reliance on unspecified behaviour. Unspecified > behaviour is allowed to change. > > I am sure you have read (and ignored) the following guarantee taken from > http://sqlite.org/c3ref/column_name.html : My questions are thes

Re: [sqlite] Minor bug reports during build.

2017-12-22 Thread Michael Tiernan
"Working as advertised" Okay, that's just funny. That it doesn't build is correct? Also, despite the "disable-tcl" flag, the tests all fail because of something involving tcl. Don't think I read that in the advertisement. Just as an FYI, it builds correctly on MacOSX and doesn't complain about th

Re: [sqlite] What happens if an in memory database runs out of memory

2017-12-22 Thread curmudgeon
>I would think that a temp file database (created with an empty string) is no different from a regular disk file resident database EXCEPT that the file is generated with an random tmpfile name and automatically unlinked when closed, and that "memory pressure" equates to "page cache is full". I don

Re: [sqlite] What happens if an in memory database runs out of memory

2017-12-22 Thread Keith Medcalf
>I thought I had posted this earlier but I don't see it. >Earlier I said the ideal solution would be something that uses memory >and defaults to disc if it runs out of memory. In response Richard's >suggested using a temp database with a blank name as that would use >memory but parts of it would

Re: [sqlite] Atomic DELETE index optimisation?

2017-12-22 Thread Dinu
Thank you all for the replies, I will hack this problem one way or another after the hoildays and let you know how it went. In the mean time, I wish you all happy peaceful holidays, and a great New Year! Dinu -- Sent from: http://sqlite.1065341.n5.nabble.com/ ___

Re: [sqlite] [EXTERNAL] Re: Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread Radovan Antloga
How do you test your sql-s? I write sql from step to step from very simple to complex. So I have select and finally I need table for that. It was simple until now. Just put create table as before select and you get same result (same names) as in select. Your example is not the same. If using expr

Re: [sqlite] [EXTERNAL] Re: Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread R Smith
On 2017/12/22 11:06 AM, Radovan Antloga wrote: I'm using sqlite from version 2. I have 1000+ sql-s written already. I understand that outermost statement must have AS clause as I have explained below (select d as d ...). Sqlite authors always say that new version can not break sql-s for milions

Re: [sqlite] [EXTERNAL] Re: Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread Radovan Antloga
But column name is specified in inner select with AS clause. It can be used in outer select and work as expected. select d from (select c AS d from (select a AS c from test)); I hope you did read my example. You can see explicitly defined name in select a AS c from test then again explicitly d

Re: [sqlite] [EXTERNAL] Re: Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread Hick Gunter
The problem lies in your reliance on unspecified behaviour. Unspecified behaviour is allowed to change. I am sure you have read (and ignored) the following guarantee taken from http://sqlite.org/c3ref/column_name.html: "Column Names In A Result Set ... The name of a result column is the value o

Re: [sqlite] What happens if an in memory database runs out of memory

2017-12-22 Thread curmudgeon
I thought I had posted this earlier but I don't see it. Earlier I said the ideal solution would be something that uses memory and defaults to disc if it runs out of memory. In response Richard's suggested using a temp database with a blank name as that would use memory but parts of it would be flu

Re: [sqlite] [EXTERNAL] Re: Changed behaviour or bug using field alias in 3.21.0

2017-12-22 Thread Radovan Antloga
I'm using sqlite from version 2. I have 1000+ sql-s written already. I understand that outermost statement must have AS clause as I have explained below (select d as d ...). Sqlite authors always say that new version can not break sql-s for milions of users using sqlite. But this change does. Sor

Re: [sqlite] Importing Text to Create a Table

2017-12-22 Thread Chris Locke
What operating system are you using, and what software are you using to do the import? What specificially are you trying to import? If you perform a sequence of 'insert' statements, then that can be time consuming - its better to incorporate them into one 'transaction' - sqlite bundles the operati

Re: [sqlite] Importing Text to Create a Table

2017-12-22 Thread Luuk
Can you give a (short) example of some lines, and how you import them? Creating a table with 1 field text 255 seems not the right way to do this if you are only interested in emailaddresses. On 22-12-17 01:22, Lawrence Murphy wrote: > I am supporting a website which aims to protect a forest fro