[sqlite] Re: Re[sqlite] garding software of SQlite2.1

Hi, Thank you very much for your response.I tried to convert SQLite2.1 version to SQlite3 version but unable to convert them .Could you please explain in which command prompt we need to convert them.From given url we found only .exe file not software.We need software .If we convert them into

Re: Re[2]: [sqlite] Mechanism for pre-allocating contiguous files for Sqlite?

Hi Teg, Isn't an open issued for the database and journal separately? I'm very familiar with the behavior for read-only, not so much for read/write... Regards, -- Gary On 10/28/07, Teg <[EMAIL PROTECTED]> wrote: > > Hello Gary, > > Sunday, October 28, 2007, 4:51:11 PM, you wrote: > > GM> Hi

Re[2]: [sqlite] Mechanism for pre-allocating contiguous files for Sqlite?

Hello Gary, Sunday, October 28, 2007, 4:51:11 PM, you wrote: GM> Hi Teg, GM> Have you considered the SQLite VFS? GM> Regards, GM> -- Gary GM> On 10/28/07, Teg <[EMAIL PROTECTED]> wrote: >> >> >> I'd like to pre-allocate the DB for Sqlite so, I can ensure it's a >> contiguous block of space

Re: AW: AW: [sqlite] INSERT OR IGNORE and sqlite3_last_insert_rowid()

On 10/28/07, Michael Ruck <[EMAIL PROTECTED]> wrote: > I'd suggest putting this into the documentation of > sqlite3_last_insert_rowid(), that > the call is not reliable in scenarios such as this one. It might be appropriate to just stress it only works for successful INSERTs. I'd just assumed

[sqlite] improving performance on SELECT

Hi everyone, I'm trying to improve SELECT queries on a db I created. Here's the part I think is relevant: create table featureSet (fsetid integer primary key, man_fsetid text, chrom text); create table pmfeature (fid integer primary key, fsetid not null references "featureSet" ("fsetid"), x

Re: [sqlite] Mechanism for pre-allocating contiguous files for Sqlite?

Hi Teg, Have you considered the SQLite VFS? Regards, -- Gary On 10/28/07, Teg <[EMAIL PROTECTED]> wrote: > > > I'd like to pre-allocate the DB for Sqlite so, I can ensure it's a > contiguous block of space on the disk. I'm aware of the "Insert a > bunch of data then delete" method but, it

[sqlite] Mechanism for pre-allocating contiguous files for Sqlite?

I'd like to pre-allocate the DB for Sqlite so, I can ensure it's a contiguous block of space on the disk. I'm aware of the "Insert a bunch of data then delete" method but, it doesn't ensure a contiguous block on disk. Is there some way I can allocate a file with OS calls and then use it as an

RE: [sqlite] Virtual table xFilter argv object longevity

Thanks Dan > -Original Message- > From: Dan Kennedy [mailto:[EMAIL PROTECTED] > Sent: Sunday, October 28, 2007 11:11 AM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Virtual table xFilter argv object longevity > > On Sun, 2007-10-28 at 14:03 +, Evans, Mark (Tandem) wrote: >

AW: AW: AW: [sqlite] INSERT OR IGNORE and sqlite3_last_insert_rowid()

I'd suggest putting this into the documentation of sqlite3_last_insert_rowid(), that the call is not reliable in scenarios such as this one. -Ursprüngliche Nachricht- Von: D. Richard Hipp [mailto:[EMAIL PROTECTED] Gesendet: Sonntag, 28. Oktober 2007 17:48 An: sqlite-users@sqlite.org

AW: AW: AW: [sqlite] INSERT OR IGNORE and sqlite3_last_insert_rowid()

Good point. Thanks. -Ursprüngliche Nachricht- Von: D. Richard Hipp [mailto:[EMAIL PROTECTED] Gesendet: Sonntag, 28. Oktober 2007 17:48 An: sqlite-users@sqlite.org Betreff: Re: AW: AW: [sqlite] INSERT OR IGNORE and sqlite3_last_insert_rowid() On Oct 28, 2007, at 10:59 AM, Michael Ruck

Re: AW: AW: [sqlite] INSERT OR IGNORE and sqlite3_last_insert_rowid()

On Oct 28, 2007, at 10:59 AM, Michael Ruck wrote: Yes, I am well aware of this possibility as I've written in my initial mail. It just doesn't fit with the description of sqlite3_last_insert_rowid() in my understanding. I think this is a bug - either in the documentation or in the

Re: [sqlite] Virtual table xFilter argv object longevity

On Sun, 2007-10-28 at 14:03 +, Evans, Mark (Tandem) wrote: > The question is what is the lifetime of sqlite3_value objects passed as > argv array to the xFilter virtual table module call? Can I save the > pointers and reference the values for constraint testing in my > implementation of

AW: AW: [sqlite] INSERT OR IGNORE and sqlite3_last_insert_rowid()

Yes, I am well aware of this possibility as I've written in my initial mail. It just doesn't fit with the description of sqlite3_last_insert_rowid() in my understanding. I think this is a bug - either in the documentation or in the implementation. sqlite3_last_insert_rowid() should return the

Re: AW: [sqlite] INSERT OR IGNORE and sqlite3_last_insert_rowid()

[Default] On Sun, 28 Oct 2007 10:00:52 +0100, "Michael Ruck" <[EMAIL PROTECTED]> wrote: >Hi, > >I did specify UNIQUE for category. The id is also kept, so everything is >working >*except* that I don't get the id of the record ignored from >sqlite3_last_insert_rowid(). > >Mike You could simply

[sqlite] Virtual table xFilter argv object longevity

The question is what is the lifetime of sqlite3_value objects passed as argv array to the xFilter virtual table module call? Can I save the pointers and reference the values for constraint testing in my implementation of xNext? Fingers crossed. Many thanks, Mark

AW: [sqlite] INSERT OR IGNORE and sqlite3_last_insert_rowid()

Hi, I did specify UNIQUE for category. The id is also kept, so everything is working *except* that I don't get the id of the record ignored from sqlite3_last_insert_rowid(). Mike -Ursprüngliche Nachricht- Von: Kees Nuyt [mailto:[EMAIL PROTECTED] Gesendet: Samstag, 27. Oktober 2007