Re: [sqlite] SqlAlchemy 0.9 release note complaint

Python 3.4 last beta3 is planned for January 26, 2014 Current SQLite in Python3.4 beta2 is 3.8.1. Unless a miracle occurs these next few days, we will not see CTE in standard Python before 2 years more. ___ sqlite-users mailing list

Re: [sqlite] Lightweight integrity_check?

On 15 Jan 2014 at 19:20, Steven Fisher wrote: > After opening, I want to do some basic checking of my database. > > I’m finding integrity_check much too slow for some of my users (especially > with large amounts of data) but I don’t want to just blindly trust the > database

Re: [sqlite] Case Insensitive Defect with New Query Planner

On Wed, Jan 15, 2014 at 6:13 PM, Chris Swinefurth wrote: > The query: > SELECT terms.term, terms.id, terms.type, terms.product_id FROM terms > JOIN products ON terms.product_id = products.id JOIN > sub_categories ON products.category_id = sub_categories.id WHERE

[sqlite] Case Insensitive Defect with New Query Planner

Guys, I’ve identified a detrimental query planner change between 3.7.12 and 3.8.1. It appears to be a change from the 3.8 NGQP. A query with a like where clause with “collate nocase” now uses a full table scan instead of a covering index. This occurs even if the case_sensitive_like

Re: [sqlite] Insert multiple values as an economy of coding time and quicker upload process ?

>I'm not an expert in SQLite extension. >Unless I missed something, Wholenumber seems apparently not embeded >into SQLite for python : >CREATE VIRTUAL TABLE nums USING wholenumber; >SELECT value FROM nums WHERE value<1; >SELECT value FROM nums WHERE value BETWEEN 100 AND 500 >gives : >

[sqlite] AUTO: Oren Bar is out of the office - He is in vacation (returning 27/02/2014)

I am out of the office until 27/02/2014. I will be unavailable. For CDS issues, please contact Asaf Levy. For PT issues, please contact Elena Drobchenko. Note: This is an automated response to your message "Re: [sqlite] How to bind parameters to LIKE with sqlite3_bind_text?" sent on

Re: [sqlite] SqlAlchemy 0.9 release note complaint

Yes, just changing the DLL is safe. I believe the default DLL might need to be compiled with SQLITE_ENABLE_COLUMN_METADATA. I replace the sqlite3.dll in Python all the time to keep it up-to-date with the latest head. >-Original Message- >From: sqlite-users-boun...@sqlite.org

Re: [sqlite] Lightweight integrity_check?

On 01/16/2014 02:20 AM, Steven Fisher wrote: After opening, I want to do some basic checking of my database. I’m finding integrity_check much too slow for some of my users (especially with large amounts of data) but I don’t want to just blindly trust the database either. A few options: -

[sqlite] Lightweight integrity_check?

After opening, I want to do some basic checking of my database. I’m finding integrity_check much too slow for some of my users (especially with large amounts of data) but I don’t want to just blindly trust the database either. A few options: - Rely on what sqlite does on its own when I start

Re: [sqlite] SqlAlchemy 0.9 release note complaint

On Wed, Jan 15, 2014 at 1:53 PM, big stone wrote: > Ok, > > The problem is fixed starting SQLite 3.7.16, > But Python 3.3 series (up to 3.3.3) seems to be shipped with the very old > SQLite 3.7.12, by default. > > Is there a simple trick to "upgrade" SQLite3 version used by

Re: [sqlite] SqlAlchemy 0.9 release note complaint

Ok, The problem is fixed starting SQLite 3.7.16, But Python 3.3 series (up to 3.3.3) seems to be shipped with the very old SQLite 3.7.12, by default. Is there a simple trick to "upgrade" SQLite3 version used by Python (under windows) ? Just changing the sqlite3.dll is safe ?

Re: [sqlite] Insert multiple values as an economy of coding time and quicker upload process ?

I'm not an expert in SQLite extension. Unless I missed something, Wholenumber seems apparently not embeded into SQLite for python : CREATE VIRTUAL TABLE nums USING wholenumber; SELECT value FROM nums WHERE value<1; SELECT value FROM nums WHERE value BETWEEN 100 AND 500 gives :

Re: [sqlite] How to bind parameters to LIKE with sqlite3_bind_text?

On Wed, Jan 15, 2014 at 4:41 PM, Clemens Ladisch wrote: > sqliteuser wrote: > > sqlite3_bind_text(stmt, 1, qry.c_str(), -1, 0); > > The last parameter must not be zero. For string::c_str(), you > should use SQLITE_TRANSIENT. > Depending on the context, SQLITE_STATIC

Re: [sqlite] Serialization and threading

Reza Housseini wrote: > The execution looks as follow: > > sqlite3_step(beginstmt); > sqlite3_step(vectorstmt); > sqlite3_step(intrstmt); > sqlite3_step(commitstmt); So your program does not check error codes? Regards, Clemens ___

Re: [sqlite] Load spatialite-extension through System.Data.SQLite

On Tue, 14 Jan 2014 20:54:54 +0100, Markus Dibo wrote: I am trying to use SQLite/Spatialite from a .Net-4.0-Application. To get easy access to SQLite I am using System.Data.SQLite. I try to load version 4.1.1 of Spatialite via the command-text "**SELECT load_extension("libspatialite-4.dll")"

Re: [sqlite] Serialization and threading

On 1/14/2014 2:41 AM, Reza Housseini wrote: But now it seems that not every interaction is logged into the database (I also log the data in a std container). As I understand with the serialization option multiple threads can have access to the same database connection and statement, and sqlite

Re: [sqlite] How to bind parameters to LIKE with sqlite3_bind_text?

On 1/14/2014 8:10 AM, sqliteuser wrote: what is the proper way to bind string to LIKE statement? The same way you bind any other string parameter. The fact that the parameter happens to be used as an operand of a LIKE operator is irrelevant. std::string qry = "SELECT name "

Re: [sqlite] Urdu Language Support

On 1/15/2014 8:25 AM, Rehan Siddiqui wrote: Does Sqlite support Urdu language. We want to put a lot of urdu text data in our software. Depends on what you mean by "support". SQLite can store arbitrary Unicode strings, whether containing characters used in Urdu or any others. If you need,

[sqlite] Urdu Language Support

Hi, Does Sqlite support Urdu language. We want to put a lot of urdu text data in our software. Regards ___ sqlite-users mailing list sqlite-users@sqlite.org

[sqlite] How to bind parameters to LIKE with sqlite3_bind_text?

Hi, what is the proper way to bind string to LIKE statement? For some reason i get no results: I can bind int's just fine (not with LIKE though). std::string qry = "SELECT name " " FROM Person " " WHERE name LIKE ? "; sqlite3_prepare_v2 (...)

[sqlite] Serialization and threading

Hello I want to use sqlite to log some data into a simple table. My application is multi-threaded but I only need to write to the database. I begin with specifying the statements. const char *vectorsql = "INSERT INTO vector (x0,x1,x2) VALUES (?,?,?);"; const char *intrsql = "INSERT INTO

[sqlite] Bug Report SQLITE JDBC driver 3.7.2: problem calling "wasNull" function in the ResultSet.

Hi, if the user calls "getObject" before calling wasNull then wasNull returns either the "wasNull" value of the previous called get call, or it throws an Exception, if it is called the first time. How to replicate this bug: DBConnection conn = DatabaseMetaData md = conn.getMetaData();

Re: [sqlite] Insert multiple values as an economy of coding time and quicker upload process ?

> >INSERT INTO t1 SELECT 1 UNION SELECT 2 UNION (...) SELECT ; > >It works out of the box on any DBMS you care to name, and of course in >SQLite, too. It is ever so slightly verbose, but better than the >alternative of executing INSERT INTO t1 VALUES(###); > Of course, if your

Re: [sqlite] shell crashes when there is no column name

On Wed, Jan 15, 2014 at 6:48 AM, Clemens Ladisch wrote: > > And a NULL column name is considered a bug: > > > Not so much a "bug" as "undesirable". Note that even with the change referenced above, sqlite3_column_name() might

Re: [sqlite] shell crashes when there is no column name

Klaas V wrote: > Clemens wrote: >> $ sqlite3 >> SQLite version 3.8.3 2014-01-11 12:52:25 >> Enter ".help" for instructions >> Enter SQL statements terminated with a ";" >> sqlite> .header on >> sqlite> values(1); >> (null) >> 1 >> sqlite> .mode html >> sqlite> values(1); >> Segmentation

Re: [sqlite] SqlAlchemy 0.9 release note complaint

On Wed, Jan 15, 2014 at 1:50 AM, big stone wrote: > Hello, > > Reading SQLAlchemy release note, I see a functionality complaint on SQLite. > > see :http://docs.sqlalchemy.org/en/rel_0_9/changelog/migration_09.html > > > In its last release Note, SQLAlchemy complains that

Re: [sqlite] shell crashes when there is no column name

Clemens wrote: >  $ sqlite3 >  SQLite version 3.8.3 2014-01-11 12:52:25 >  Enter ".help" for instructions >  Enter SQL statements terminated with a ";" >  sqlite> .header on >  sqlite> values(1); >  (null) >  1 >  sqlite> .mode html >  sqlite> values(1); >  Segmentation fault One runs the risk