Sadly, I have narrowed down the issue to some sort of memory clash
between the SQLite3 DLL and the EXE that is calling our plugin
I can change the code to retrieve data from almost *anything*
else from faked random data created on the fly, through ASCII CSV
files loaded into TStringLists to
Exactly what are you calling sqlite3_free() on?
--- Chris Schirlinger <[EMAIL PROTECTED]> wrote:
> Sadly, I have narrowed down the issue to some sort of memory clash
> between the SQLite3 DLL and the EXE that is calling our plugin
>
> I can change the code to retrieve data from almost *anythin
On 6 Apr 2005 at 3:13, Dan Kennedy wrote:
Date sent: Wed, 6 Apr 2005 03:13:58 -0700 (PDT)
From: Dan Kennedy <[EMAIL PROTECTED]>
Subject:Re: [sqlite] Access Violations in sqlite3_step when in
DLL
To: sqlite-users@sqlite.org, [EMAIL
Hello,
I've been looking into upgrading to 3.2.1 from 2.8.15 and am still
running into problems with returned column names.
I've written a piece of code to test four scenarios with 2.8.15 and
3.2.1 and these are the results:
Two tables:
CREATE TABLE A_TABLE (col1 INTEGER, col2 INTEGER)
CREATE
--- Chris Schirlinger <[EMAIL PROTECTED]> wrote:
> On 6 Apr 2005 at 3:13, Dan Kennedy wrote:
>
> Date sent:Wed, 6 Apr 2005 03:13:58 -0700 (PDT)
> From: Dan Kennedy <[EMAIL PROTECTED]>
> Subject: Re: [sqlite] Access Violations in sqlite3_step when in
> DLL
> Someone also mentioned ram. The machine(s) we are using seem stable
> for other processes but won't rule that out
http://memtest86.com/
Mine was perfectly stable too, until I tried a certain operation
and it always failed on it.
Many years ago I had a memory chip that could be written to and
-- de f <[EMAIL PROTECTED]> wrote:
> Thanks Jay.
>
> Great! This could work...
>
> I'm wondering, though if you know whether the limitation below
> (from sqlite documentation) could be safely circumvented if
> attaching the source db with an alias name. It seems to work
> when i try it but I'm
Kurt Welgehausen wrote:
begin immediate; insert; select max(id) from blah; commit;
Or "select last_insert_rowid() from blah limit 1"
Regards
Better yet
select last_insert_rowid();
The from clause is not needed and may imply that SQLite keeps the last
inserted rowid for each table, which
> >>begin immediate; insert; select max(id) from blah; commit;
> >>
> >>
> >
> >Or "select last_insert_rowid() from blah limit 1"
> >
> >Regards
> >
> >
> >
> Better yet
>
> select last_insert_rowid();
>
> The from clause is not needed and may imply that SQLite keeps the
> last
> inse
How feasible would it be to use triggers as a way to implement record
locking in SQLite? It seems like if you create a BEFORE trigger for a
particular record id and have that trigger RAISE an error for updates
and deletes, you've basically locked the record. Hmm. I guess the
problem is that the rec
On Apr 6, 2005 10:43 AM, Will Leshner <[EMAIL PROTECTED]> wrote:
> How feasible would it be to use triggers as a way to implement record
> locking in SQLite? It seems like if you create a BEFORE trigger for a
> particular record id and have that trigger RAISE an error for updates
> and deletes, you
11 matches
Mail list logo
