Re: [sqlite] Compiler warnings with Sun Studio 12.1 on Solaris 10

D. Richard Hipp wrote: >> Thank you. >> >> I understand you can't fix these warnings since you don't have >> access to >> such machines. Would you like access? If so, I can give you access >> to a >> 16-core Sun T5240 at the university of Washington, with runs Solaris >> 10 >> update 7

Re: [sqlite] performance trending

On 29 Sep 2009, at 3:07am, oryann9 wrote: > Is there a method, set of tools to gather and show either > graphically or non-graphically the performance of SQLite3 databases? > I am trying to determine the current memory, disk IO and cpu load > all DB transactions place on our server. Because

[sqlite] performance trending

Is there a method, set of tools to gather and show either graphically or non-graphically the performance of SQLite3 databases? I am trying to determine the current memory, disk IO and cpu load all DB transactions place on our server. thank you!

[sqlite] transactions in one thread

I need to be able to see the committed version of a database while a new transaction is in the works. I would like to open the same database file twice in a single thread, start a transaction on one of the database connections, make a few writes to that database, then on the other database

Re: [sqlite] feature request - field exclusion list in select list

Stephan Wehner wrote: > On Sun, Sep 27, 2009 at 5:19 PM, Darren Duncan > wrote: > >> Following my previous message to the sqlite-users list, I've done a bit more >> research and decided to escalate my reply to a formal feature request. >> >> I was initially going to

Re: [sqlite] SELECT ALL BUT syntax (was Re: less typing possible ?)

thanks Darren, Darren Duncan wrote: > Stef Mientki wrote: > >> hello, >> >> I often want to see most of the columns of a table / view / query, but a >> few I don't want to see. >> So I now create a huge list of fields, >> but isn't there a more typo-frindly way, like : >> >> select * -

Re: [sqlite] building permanently loaded extensions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 P Kishor wrote: > So, here it is again -- how can I convert a loadable extension to a > permanently loaded extension? A tutorial, por favor. Look at how RTree, FTS3 and ICU are done with the amalgamation. Roger -BEGIN PGP SIGNATURE- Version:

Re: [sqlite] building permanently loaded extensions

On Mon, Sep 28, 2009 at 1:21 PM, Nuno Lucas wrote: > P Kishor wrote: >> Sometime back I had asked the following question, and it seems to have >> gotten Warnocked (http://en.wikipedia.org/wiki/Warnock's_Dilemma) >> >> So, here it is again -- how can I convert a loadable

Re: [sqlite] building permanently loaded extensions

P Kishor wrote: > Sometime back I had asked the following question, and it seems to have > gotten Warnocked (http://en.wikipedia.org/wiki/Warnock's_Dilemma) > > So, here it is again -- how can I convert a loadable extension to a > permanently loaded extension? A tutorial, por favor. I believe

Re: [sqlite] building permanently loaded extensions

Sometime back I had asked the following question, and it seems to have gotten Warnocked (http://en.wikipedia.org/wiki/Warnock's_Dilemma) So, here it is again -- how can I convert a loadable extension to a permanently loaded extension? A tutorial, por favor. On Wed, Sep 16, 2009 at 10:25 PM, P

Re: [sqlite] Tedious CSV import question

On Mon, Sep 28, 2009 at 12:13 PM, Petite Abeille wrote: > > On Sep 27, 2009, at 7:35 PM, Nuno Lucas wrote: > >> Some time ago I had to do something similar and decided to write a >> small >> virtual table implementation to treat CSV files as just another table. > > Very

Re: [sqlite] Optimise select from attached databases

On Mon, Sep 28, 2009 at 12:31 PM, Andrew Gatt wrote: > P Kishor wrote: >> On Mon, Sep 28, 2009 at 12:06 PM, Andrew Gatt wrote: >> >>> I'm trying to optimise a select statement, but from multiple attached >>> databases. The general statement would be;

Re: [sqlite] Optimise select from attached databases

P Kishor wrote: > On Mon, Sep 28, 2009 at 12:06 PM, Andrew Gatt wrote: > >> I'm trying to optimise a select statement, but from multiple attached >> databases. The general statement would be; >> >> SELECT * FROM database0.table WHERE id = 1; >> >> Where i have a long

Re: [sqlite] Tedious CSV import question

On Sep 27, 2009, at 7:35 PM, Nuno Lucas wrote: > Some time ago I had to do something similar and decided to write a > small > virtual table implementation to treat CSV files as just another table. Very nice :) Similar to Oracle's "external table": "External Tables"

Re: [sqlite] Optimise select from attached databases

On Mon, Sep 28, 2009 at 12:06 PM, Andrew Gatt wrote: > I'm trying to optimise a select statement, but from multiple attached > databases. The general statement would be; > > SELECT * FROM database0.table WHERE id = 1; > > Where i have a long list of ids to retrieve, which

[sqlite] Optimise select from attached databases

I'm trying to optimise a select statement, but from multiple attached databases. The general statement would be; SELECT * FROM database0.table WHERE id = 1; Where i have a long list of ids to retrieve, which could be from any of the attached databases. With a single database i would prepare the

Re: [sqlite] Sqlite testing

I'd like to help, but you've not provided any relevant information. Obviously, in order to test, you're going to need to resolve your build failure. SQLite version, compiler, compiler options, compiler output, etc. would all be useful towards this end. -Shane On Fri, Sep 25, 2009 at 12:17 AM,

Re: [sqlite] normalization example(s)

Don't get carried away with keys, triggers and stuff like that at this point. For a start off your example is not normalised. You would have a person table and a food table but then you will need a person-food table as the relationship between person and food is many-to-many so you have to break

Re: [sqlite] Sqlite testing

I'd like to help, but you've not provided any relevant information. Obviously, in order to test, you're going to need to resolve your build failure. SQLite version, compiler, compiler options, compiler output, etc. would all be useful towards this end. -Shane On Fri, Sep 25, 2009 at 12:17 AM,

Re: [sqlite] normalization example(s)

On Mon, Sep 28, 2009 at 10:28 AM, John wrote: > CityDev wrote: >> You seem to be asking about four separate issues - normalisation,  table >> creation, table loading, and SQLite syntax. The thing is I've just looked at >> your book's index and I can't imagine a better source

Re: [sqlite] normalization example(s)

CityDev wrote: > You seem to be asking about four separate issues - normalisation, table > creation, table loading, and SQLite syntax. The thing is I've just looked at > your book's index and I can't imagine a better source of answers to your > questions. > > Maybe you would like to post some

Re: [sqlite] How do you check if the linker is the GNU linker?

Hi, Dave! That piece of code comes from the macros inserted by the libtool support. Normally, you should find the macro in /usr/share/aclocal/lib-ld.m4 (at least on Fedora, Debian, and Gentoo.) In case it's not there, I've reproduced the M4 macro below. Please note that it's licensed as

Re: [sqlite] Compiler warnings with Sun Studio 12.1 on Solaris 10

On Sep 28, 2009, at 10:15 AM, Dr. David Kirkby wrote: > Roger Binns wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Dr. David Kirkby wrote: >>> "sqlite3.c", line 18731: warning: integer overflow detected: op "<<" >>> "sqlite3.c", line 18748: warning: integer overflow detected:

[sqlite] How do you check if the linker is the GNU linker?

I notice when configuring sqlite that you check if the GNU linker is the GNU linker. I'd like to pinch that bit of code from you, but I don't see anything in configure.ac for this. Is this something you have hard-crafted into the configure script? Dave

Re: [sqlite] Compiler warnings with Sun Studio 12.1 on Solaris 10

Roger Binns wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Dr. David Kirkby wrote: >> "sqlite3.c", line 18731: warning: integer overflow detected: op "<<" >> "sqlite3.c", line 18748: warning: integer overflow detected: op "<<" >> "sqlite3.c", line 32546: warning: statement not

Re: [sqlite] Access violation in sqlite3.dll

That sounds reasonable. But I 've deleted code which can provide evidence. That's all,it's just a homework. Thanks! ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Access violation in sqlite3.dll

I believe your changes mean that your database handler pDoc->m_db wasn't open before the call to CMainView::myUpdateView() despite you thought so. Pavel On Mon, Sep 28, 2009 at 9:12 AM, meng wei wrote: > THANKS VERY MUCH for so exhaustive reply! :-) > > I made my program

Re: [sqlite] Access Violation in sqlite3.dll

Thanks! > This line shouldn't compile unless you really meant > ::sqlCallback_UpdateList as the 3rd parameter. I reallly meant it as the 3rd parameter. I have made my program run but don't why,as I've wrote in the reply to Pavel. > Do you understand that this output is useless? What would be

Re: [sqlite] Access violation in sqlite3.dll

THANKS VERY MUCH for so exhaustive reply! :-) I made my program run before I saw your reply, but I can't understand how it works. The problem seems to be caused by the 1st parameter of sqlite3_exec. sqlite3_exec(pDoc->m_db,pDoc->m_strSQL,sqlCallback_UpdateList , 0, &(pDoc->m_pErrMsg)); I changed

Re: [sqlite] Access violation in sqlite3.dll

Hi, Meng. The problem is that you are passing a C++ class method to sqlite3_exec. sqlite3_exec expects a callback function using the CDECL calling convention, and by default class methods do not use that calling convention when compiled under Visual C++ (they use thiscall, IIRC.) The reason it

Re: [sqlite] Access Violation in sqlite3.dll

> sqlite3_exec(pDoc->m_db,"select * from table1", sqlCallback_UpdateList, > 0, &(pDoc->m_pErrMsg)); This line shouldn't compile unless you really meant ::sqlCallback_UpdateList as the 3rd parameter. > I met no problem with win32 console application,but when it turn to MFC > in Visual C++,the

Re: [sqlite] FTS3 phantom token?...

Thanks Marbex, Puneed and specially to Scott for the snippet() tip. 'ined' is Porter stemmed to 'in'! :-) So that is why it finds so many rows. Now, to find 17081 rows from a table with 25672, fts3 took 4.47 seconds! The query is: select title from fts_news where description match 'in'

[sqlite] Access Violation in sqlite3.dll

I met no problem with win32 console application,but when it turn to MFC in Visual C++,the same code dosen't work. *The error is:* Unhandeled exception in xxx.exe(sqlite3.dll)0xC005 Access Violation *More output:* Loaded 'ntdll.dll', no matching symbolic information found. Loaded

Re: [sqlite] FTS3 phantom token?...

Right, Puneet, this is what I mean. I tried the same query with another database with 25.600 rows: select * from fts_news where description match 'ined' the query returns 17.080 rows which is wrong because If I do: select * from fts_news where description like '% ined %' The query

Re: [sqlite] feature request - field exclusion list in select list

On 28 Sep 2009, at 5:51am, Darren Duncan wrote: > Robustness comes in several ways. One is that with less code mass > their tends > to be fewer places to have bugs, all other things equal; when you make > developers write more, they are more likely to make mistakes. > Another piece of >

Re: [sqlite] feature request - field exclusion list in select list

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Darren Duncan wrote: > The main rationale for the feature I mention is code brevity, For more context, what language are you writing your code in and how do you get the contents of each column. Using the C api there are 3 ways: 1 - Explicit:

Re: [sqlite] Sqlite reading all column data on selects.

In the relational model, the unit of access is a tuple so you would expect a DBMS to process all columns. Typically they also access in units of a page (although a tuple of course might extend across more than one page) The discussion seems to have moved onto selecting pages. Surely if you need

Re: [sqlite] normalization example(s)

You seem to be asking about four separate issues - normalisation, table creation, table loading, and SQLite syntax. The thing is I've just looked at your book's index and I can't imagine a better source of answers to your questions. Maybe you would like to post some specific cases here? --