Re: [sqlite] Using incremental BLOB I/O when processing result set

Well that is very disappointing :-( Not being able to extract a portion of a BLOB from a result set without having the complete BLOB in memory makes it impractical to use BLOBs in SQLite in a database independent manner. Its a shame that a BLOB handle is not returned as a result of a query

Re: [sqlite] SELECT from fts3 tokens, is it possible?

On Mon, Dec 28, 2009 at 8:19 PM, Dan Kennedy wrote: >> If you want the data for other purposes, you could almost implement a >> hack to get is.  For instance, "SELECT count(docid) FROM fts_table >> WHERE fts_table MATCH 'x';" is kind of close, and you could change the >>

Re: [sqlite] Using incremental BLOB I/O when processing result set

On 29 Dec 2009, at 2:18am, Igor Tandetnik wrote: > Simon Slavin wrote: >> On 29 Dec 2009, at 2:02am, Zaher Dirkey wrote: >>> If i want to extract BLOB to a file that mean it is must the whale >>> blob be loaded to memory before can save it? >> >> Yes. Also, the whole BLOB must have been in

Re: [sqlite] SELECT from fts3 tokens, is it possible?

> If you want the data for other purposes, you could almost implement a > hack to get is. For instance, "SELECT count(docid) FROM fts_table > WHERE fts_table MATCH 'x';" is kind of close, and you could change the > match to handle prefix stuff. Unfortunately, the fts vtable cursor > sets up a

Re: [sqlite] Using incremental BLOB I/O when processing result set

Simon Slavin wrote: > On 29 Dec 2009, at 2:02am, Zaher Dirkey wrote: >> If i want to extract BLOB to a file that mean it is must the whale >> blob be loaded to memory before can save it? > > Yes. Also, the whole BLOB must have been in memory in the first place, when > you saved the record. Not

Re: [sqlite] Using incremental BLOB I/O when processing result set

Zaher Dirkey wrote: > If i want to extract BLOB to a file that mean it is must the whale > blob be loaded to memory before can save it? No, not with BLOB I/O. But you have to be careful: don't mention the BLOB field in your SELECT statement, retrieve the ROWID instead. Then use it in

Re: [sqlite] Using incremental BLOB I/O when processing result set

On 29 Dec 2009, at 2:02am, Zaher Dirkey wrote: > Pavel Ivanov wrote: >> > >> Just keep in mind that if the user puts blob column into a query >> (which IIRC is required by SQLGetData) then SQLite reads full blob >> value into memory before you can do anything with that. So you're not >> with a

Re: [sqlite] Using incremental BLOB I/O when processing result set

Pavel Ivanov wrote: > > Just keep in mind that if the user puts blob column into a query > (which IIRC is required by SQLGetData) then SQLite reads full blob > value into memory before you can do anything with that. So you're not > with a good luck here anyway. > If i want to extract BLOB to a

Re: [sqlite] cross-database time function.

On 28 Dec 2009, at 8:07pm, Alexey Pechnikov wrote: > On Monday 28 December 2009 21:29:48 Simon Slavin wrote: > >> mmdd(if you need just a date) >> hhmmss (if you need just a time) >> mmddThhmmss (the date, then a 'T', then the time) > > Hm, you

[sqlite] BUG Report -- check.test has inconsistent test numbering

Documentation bug -- annoyance level Check.test has test # 4.3 listed twice do_test check-4.3 { execsql { UPDATE t4 SET x=4, y=3; SELECT * FROM t4 } } {4 3} do_test check-4.3 { execsql { UPDATE t4 SET x=12, y=2; SELECT * FROM t4 } } {12 2} Regards, Noah Hart

Re: [sqlite] cross-database time function.

Hello! On Monday 28 December 2009 21:29:48 Simon Slavin wrote: > mmdd(if you need just a date) > hhmmss (if you need just a time) > mmddThhmmss (the date, then a 'T', then the time) > Hm, you did forget the simplest way - to use unixepoch format.

Re: [sqlite] cross-database time function.

On Dec 28, 2009, at 9:29 AM, Simon Slavin wrote: On 28 Dec 2009, at 5:06pm, Israel Brewster wrote: Or perhaps some other way to extract the time of a timestamp that works in all three databases? Sorry. Each database handles time/date information differently (there's no SQL standard for

Re: [sqlite] SELECT from fts3 tokens, is it possible?

My comments around performance might be overly pedantic, I don't know. For the broad fts implementation, the cost of merging data from multiple segments is higher than one would like it to be, but the advantages gained are significant enough to make it overall worthwhile. One could implement a

Re: [sqlite] cross-database time function.

On 28 Dec 2009, at 5:06pm, Israel Brewster wrote: > Or perhaps > some other way to extract the time of a timestamp that works in all > three databases? Sorry. Each database handles time/date information differently (there's no SQL standard for doing it). You will fail to find one

Re: [sqlite] SQLitedb problem

http://www.mail-archive.com/sqlite-users@sqlite.org/msg49299.html Pavel On Mon, Dec 28, 2009 at 1:15 PM, Othman Guessous wrote: > Thanks, for your remark. I paid no attention to the mailing list. In fact, I > wanted to respond to the list. > > But, i doesn't receive

Re: [sqlite] SQLitedb problem

1. Don't reply directly to me. If you write your question to the mailing list all further discussion should take place in the list. 2. Do you realize that if you write your question to the mailing list then all members of the list will answer to the list, not directly to your e-mail? Yes, I wrote

[sqlite] cross-database time function.

I am looking for a cross-database (SQLite, PostgreSQL, MySQL) method of extracting the time portion of a timestamp. I can't just use the "time()" function, because in PostgreSQL it needs to be in quotes (or preceded by pg_catalog.) to work, while in SQLite quoting the function returns an

Re: [sqlite] Bulk Insertions allowing duplicate records even primarykey existed

Durga D wrote: >I am developing an application with Sqlite3 Database in VC++ 6.0. Here, > I tried for bulk insertions with CppSQLite3Statement. But, It's allowing > duplicate records in my database even primary key existed. > > First, I inserted 5 records with insert query and

Re: [sqlite] Bulk Insertions allowing duplicate records even primary key existed

Hi Durga, double entries in the database shouldn't work. Seems to be a bug. Are these double entries have the same content? Or is it different? As I see your are inserting the same data through to different ways, right? Artur - Am 28.12.2009, 14:04 Uhr, schrieb Durga D

Re: [sqlite] SQLitedb problem

And I also don't think there is existing a application, that was made to read unused date in an SQLite database file. Deleted data is deleted. If you still want this data, then use an editor and copy the data out. If your sqlite application browser don't show these data, then all is said,

Re: [sqlite] SQLitedb problem

What's the problem with the answers already given? Pavel On Mon, Dec 28, 2009 at 6:13 AM, Othman Guessous wrote: > Hello, > > I wait for your help. Please can you answer to me ASAP. > > Thanks, > Othman. > > On Mon, Dec 21, 2009 at 12:35 AM, Othman Guessous

Re: [sqlite] SQLitedb problem

Are these data got deleted recently? Then it was only not overwritten yet. Artur -- Am 28.12.2009, 12:13 Uhr, schrieb Othman Guessous : > Hello, > > I wait for your help. Please can you answer to me ASAP. > > Thanks, > Othman. > > On Mon, Dec 21, 2009

Re: [sqlite] SQLitedb problem

Hello, I wait for your help. Please can you answer to me ASAP. Thanks, Othman. On Mon, Dec 21, 2009 at 12:35 AM, Othman Guessous wrote: > Hello, > > I have a problem with a sqlitedb file. So there is some data in this > sqlitedb file (on notepad or pspad we can

[sqlite] Bulk Insertions allowing duplicate records even primary key existed

Hi All, I am developing an application with Sqlite3 Database in VC++ 6.0. Here, I tried for bulk insertions with CppSQLite3Statement. But, It's allowing duplicate records in my database even primary key existed. First, I inserted 5 records with insert query and transactions for every

Re: [sqlite] Using incremental BLOB I/O when processing result set

> The implementation for the SQLite ODBC driver does not use incremental > BLOB I/O, it reads a BLOB into memory for each row > fetched. Not much use if the size of each image in the SQLite database > is 3gb and you only have 2gb memory. I'm looking for a solution that > will work on BLOBs larger