Re: [sqlite] Case-sensitivity, performance and LIKE

On 1 Apr 2010, at 2:55am, Rashed Iqbal wrote: > Thank you, all for your responses. I did not have access to table > definition so I used collate no-case within statements. However, I still > have very slow performance of the DB. If you are using a different collation to the one the column is

Re: [sqlite] no modlue named _sqlite error using phyton and pysqlite2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marcelo Reyes wrote: > I downloaded pysqlite2 module, There is a dedicated Python SQLite mailing list at http://groups.google.com/group/python-sqlite > but when I ran my code I get a "No module named _sqlite error". That indicates that the binary

Re: [sqlite] Berkeley DB adds SQL using SQLite API !!

On Wed, Mar 31, 2010 at 06:16:13PM -0700, Jim "Jed" Dodgen wrote: > On Wed, Mar 31, 2010 at 8:50 AM, Wiktor Adamski > >> (3) Each table and index is in a > >> separate file so your "database" was a directory full of files instead > >> of a single file > > > > This one is not a problem. Actually I

Re: [sqlite] Berkeley DB adds SQL using SQLite API !!

Thursday, April 1, 2010, 12:16:13 PM, you wrote: JJD> On Wed, Mar 31, 2010 at 8:50 AM, Wiktor Adamski JJD> wrote: >>> There were many problems with >>> that approach: >> ... >>> (3) Each table and index is in a >>> separate file so your "database" was a directory

Re: [sqlite] Case-sensitivity, performance and LIKE

Thank you, all for your responses. I did not have access to table definition so I used collate no-case within statements. However, I still have very slow performance of the DB. I ran my application using Intel's VTune performance analyzer and about 90% of time is being spent in the file sqlite.c.

Re: [sqlite] Berkeley DB adds SQL using SQLite API !!

On Wed, Mar 31, 2010 at 8:50 AM, Wiktor Adamski wrote: >> There were many problems with >> that approach: > ... >> (3) Each table and index is in a >> separate file so your "database" was a directory full of files instead >> of a single file > > This one is not a

[sqlite] no modlue named _sqlite error using phyton and pysqlite2

Hello, I downloaded pysqlite2 module, but when I ran my code I get a "No module named _sqlite error". I'm using python 2.5 and Windows XP. I need to load spatialite library and thats why I want to upgrade the sqlite3 module that comes with python 2.5 Can anyone help me? thanks. Here's the code:

Re: [sqlite] Fwd: Sqlite3 crashing on multithreaded program

> -Original Message- > From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users- > boun...@sqlite.org] On Behalf Of Jens Miltner > Sent: Wednesday, March 31, 2010 8:17 PM > To: General Discussion of SQLite Database > Subject: Re: [sqlite] Fwd: Sqlite3 crashing on multithreaded program

Re: [sqlite] Transactions + .read

On 31 Mar 2010, at 6:39pm, Kevin M. wrote: >>> So, is there an API or query I can run to load an sql file all in one go >>> (one transaction) without having to read in the file manually and query one >>> line at a time? > >> No, sorry. That's what programming languages are for. Open the

Re: [sqlite] Transactions + .read

>> Actually I was wanting to put that into a program. > I don't know how I guessed that but I'm feeling really smug now. I'm feeling very amused by your smugness ;-) >> So, is there an API or query I can run to load an sql file all in one go >> (one transaction) without having to read in the

[sqlite] A proposed change to SQLITE_STMTSTATUS_FULLSCAN_STEP

The sqlite3_stmt_status() interface with the SQLITE_STMTSTATUS_FULLSCAN_STEP operator returns the number of full- table scan steps that occurred during the evaluation of a prepared statement. This information can be used by debugging logic within an application to help locate cases where

Re: [sqlite] Transactions + .read

On 31 Mar 2010, at 4:48pm, Kevin M. wrote: >> Warning: From your phrasing it's possible you're thinking of putting a >> '.read' command into your program. The '.read' command is only a command to >> the command-line tool. It's not a function of SQLite, and you can't submit >> it as a query

Re: [sqlite] Select * from tablename results in an exception

Hi Pavel, Thank you for the background information. It helps me understand what I observed. Thanks again, Joe Joe Burnett | Principal Software Engineer | FIDELITY INSTITUTIONAL TECHNOLOGY 2 Contra Way Merrimack, NH 03054 603.791.5113 cell: 603.289.0481 -Original Message- From:

Re: [sqlite] Berkeley DB adds SQL using SQLite API !!

> There were many problems with   > that approach: ... > (3) Each table and index is in a   > separate file so your "database" was a directory full of files instead   > of a single file This one is not a problem. Actually I don't see how 1 file is better than 1 directory. For example mac

Re: [sqlite] Transactions + .read

> Warning: From your phrasing it's possible you're thinking of putting a > '.read' command into your program. The '.read' command is only a command to > the command-line tool. It's not a function of SQLite, and you can't submit > it as a query in your program. > Simon. Actually I was

Re: [sqlite] Transactions + .read

On 31 Mar 2010, at 4:21pm, Kevin M. wrote: > Hopefully I'm not duplicating a question, but I looked on sqlite.org and did > not find the answer... > > Will this: > BEGIN TRANSACTION; > .read somefile.sql > END TRANSACTION; > > Put everything in the sql file into one transaction? Or do I need

Re: [sqlite] Select * from tablename results in an exception

> I had issues in my SQLite DB schema - VARCHAR(64) was not big enough. Just a note: SQLite doesn't impose any limits on text columns. So for SQLite VARCHAR(64) is the same type as VARCHAR(1234567), and both types can accept strings of any length. Apparently your .NET library parsed declared type

[sqlite] Transactions + .read

Hopefully I'm not duplicating a question, but I looked on sqlite.org and did not find the answer... Will this: BEGIN TRANSACTION; .read somefile.sql END TRANSACTION; Put everything in the sql file into one transaction? Or do I need to put the BEGIN/END TRANSACTION statements in the sql file

Re: [sqlite] bug: output contains values of a column not listed in SELECT

On Mar 31, 2010, at 10:23 AM, Kirill Simonov wrote: > Hi, > > I encountered a weird bug. My query has the form > SELECT col_x, ... FROM my_table ... GROUP BY 1 > but the output of the query looks as if it was produced by a query of > the form > SELECT col_y, ... FROM my_table ... GROUP

[sqlite] Typo in SQLite documentation

Hi there! I just spotted a typo in the SQLite documentation at http://www.sqlite.org/lang_datefunc.html "SQL As Understood By SQLite: Date And Time Functions" In the "Examples" section, Compute the number of days since the signing of the US Declaration of Independent. SELECT

Re: [sqlite] Fwd: Sqlite3 crashing on multithreaded program

Am 31.03.2010 um 15:14 schrieb Dan Kennedy: > > > Begin forwarded message: > >> From: "Periasamy, Karthikeyan" >> Date: March 31, 2010 7:52:55 PM GMT+07:00 >> To: "danielk1...@gmail.com" >> Subject: Re: [sqlite] Sqlite3 crashing on

[sqlite] Intermittent "database or disk is full" errors with BEGIN EXCLUSIVE on windows

Occasionally a user is getting a "database or disk is full" during the call to start an exclusive transaction. My conditions: - The disk has plenty of space. - I'm using persistent journaling mode. I'm assuming this is due to some antivirus or other process holding the file and causing this

[sqlite] Fwd: Sqlite3 crashing on multithreaded program

Begin forwarded message: > From: "Periasamy, Karthikeyan" > Date: March 31, 2010 7:52:55 PM GMT+07:00 > To: "danielk1...@gmail.com" > Subject: Re: [sqlite] Sqlite3 crashing on multithreaded program > > Hi, > > Thanks for your reply. > > In

Re: [sqlite] output contains values of a column not listed inSELECT

Kirill Simonov wrote: > The following code reproduces the problem: > == > CREATE TABLE person ( > org_id TEXT NOT NULL, > nicknameTEXT NOT NULL, > license TEXT, > CONSTRAINT person_pk > PRIMARY KEY (org_id, nickname), > CONSTRAINT

[sqlite] bug: output contains values of a column not listed in SELECT

Hi, I encountered a weird bug. My query has the form SELECT col_x, ... FROM my_table ... GROUP BY 1 but the output of the query looks as if it was produced by a query of the form SELECT col_y, ... FROM my_table ... GROUP BY 1 That is, instead of values of col_x, I'm getting values of