just a little up since I have had no answers?
I'm still having the pb and cannot understand why? :)
Dennis Cote a écrit :
>
> I am forwarding this to the list in the hope that someone else will
> have a good idea since the OP, toms, is having trouble posting himself.
>
> Dennis Cote
>
> toms
I am forwarding this to the list in the hope that someone else will have
a good idea since the OP, toms, is having trouble posting himself.
Dennis Cote
toms wrote:
> ok here is the code I use for the statements:
>
> here is the SQL:
>
> "UPDATE Statistics_Players"
> " SET "
> "
Bruce Robertson wrote:
> Thanks, but I'm gonna need some further instruction or examples or pointers
> to a resource as none of these statements mean anything to me.
>
I also posted some sample code that is equivalent to the old sample code
at http://www.sqlite.org/quickstart.html which still
Bruce Robertson wrote:
> Thanks, but I'm gonna need some further instruction or examples or pointers
> to a resource as none of these statements mean anything to me.
>
Try reading this http://www.sqlite.org/cintro.html and see if it makes
more sense after that.
HTH
Dennis Cote
On Mon, Jun 09, 2008 at 03:39:01PM -0700, Bruce Robertson scratched on the wall:
> Thanks, but I'm gonna need some further instruction or examples or pointers
> to a resource as none of these statements mean anything to me.
These are C API function calls. If you're not using the C API, none
Thanks, but I'm gonna need some further instruction or examples or pointers
to a resource as none of these statements mean anything to me.
> Use this sequence:
>
> sqlite3_open
> sqlite3_prepare_v2//Compiles SQL statement
>
> loop
> sqlite3_bind... //Binds variables
>
>
Can somebody point me to documentation or examples of sqlite prepare
statements and their purose?
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
> I would expect that sqlite3_prepare would be faster in such a case, and
> maybe Toms is pointing out a circumstance where recreating the query
> seems to be faster. Or am I misreading the post?
One possible explanation (stab in the dark):
If many of the bound parameters are text (or blob)
Chiming in a thought, but isn't there a subtle difference between the two?
As I am reading Toms post, sqlite3_prepare would be called once and the
parameters would be bound up to 384 times
The call to sqlite3_exec should finalize the prepared query and
re-prepare it 384 times.
I would expect
Sqlite3_exec just encapsulates sqlite3_prepare. You very likely have
something wrong with your code if yor version works slower.
toms wrote:
> Hi all
> I tried to use the sqlite3_prepare to increase my performances during
> requests for both writing / reading.
> The strange thing is that when
Hi all
I tried to use the sqlite3_prepare to increase my performances during
requests for both writing / reading.
The strange thing is that when using prepare on a request used many
times with many parameters (many times = 384 max, many parameters = 15)
it os slower than simply using the
11 matches
Mail list logo
