Re: [PATCH] [merge-tracking] use prepared statements economically

On Thu, Aug 31, 2006 at 12:46:07AM +0530, Kamesh Jayachandran wrote:
> Daniel Berlin wrote:
> >This is fine (though mildly pointless because without being able to
> >move the entire prepared statement out of the loop, it's probably not
> >much of a speedup if at all)
> >
> I don't think so. we save the compilation cost. I believe the prepared
> statements are meant to be compiled once and the place holder values to
> be substituted based on the need(most often from the loop).
>
> Correct me if I am wrong.
>

That's the way that prepare/execute works in general.

Whether it actually has any effect in this case, you'd need to confirm
by testing (and as I think that Dan is saying, it's unlikely to make
any really significant difference in this case, at which point you
probably want to start balancing code readability against marginal
efficiency gains).

Also, can sqlite3_reset never return an error? You're not checking
for one.

Regards,
Malcolm

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 30 23:34:14 2006