You Need to bind for each insert, Sqlite does not bind by address it does a
copy.
You'll need to populate your variables inside the loop then bind then step:
prepare_v2
for(i = ...) {
assign Variables to be bound.
sqlite bind for each variable/column
s
Wednesday, March 29, 2006 6:40 AM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] sqlite3_step crash?
On Wed, 29 Mar 2006 [EMAIL PROTECTED] wrote:
>"Boris Popov" <[EMAIL PROTECTED]> wrote:
>>
>> Does this help at all?
>>
>
>No. A stack trace, espec
On Wed, 29 Mar 2006 [EMAIL PROTECTED] wrote:
>"Boris Popov" <[EMAIL PROTECTED]> wrote:
>>
>> Does this help at all?
>>
>
>No. A stack trace, especially one without line number
>information, is of no help whatsoever.
I beg to differ. Any stack trace that includes malloc or free is almost
certain
"Boris Popov" <[EMAIL PROTECTED]> wrote:
>
> Does this help at all?
>
No. A stack trace, especially one without line number
information, is of no help whatsoever.
If you think the problem is in SQLite and not in your
own code, then you should do as much of the following
as you can:
(1) Exp
. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.
Thank you.
-Original Message-
From: Boris Popov [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 28, 2006 10:32 PM
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] sqlite3_st
As a matter of fact sqlite3_reset and sqlite3_finalize also segfault if
invoked on that prepared sqlite3_stmt, so there's something seriously
screwed up, but not immediately obvious what exactly since the previous
sqlite3_column_* and sqlite3_step calls worked just fine to get all 9 rows
that are s
6 matches
Mail list logo
