An: sqlite-users@mailinglists.sqlite.org
Betreff: Re: [sqlite] [EXTERNAL] Performance impact of UPDATEing multiple
columns vs few columns
hi Darko,
>If you're preparing that statement more than once then you are wasting
time, there's no reason whatsoever to do it. You're also wasting time if
hi Darko,
>If you're preparing that statement more than once then you are wasting
time, there's no reason whatsoever to do it. You're also wasting time if you
make a bind call to set any column that hasn't changed since the last time
you executed the statement.
>The entire row is rewritten
If you're preparing that statement more than once then you are wasting time,
there's no reason whatsoever to do it. You're also wasting time if you make a
bind call to set any column that hasn't changed since the last time you
executed the statement.
The entire row is rewritten when updating
>>> Are you using a single prepared statement and binding values (in which
case, how do you know what values to bind for the "non-updated" columns?) or
are you creating query strings?
I am not too sure, if i get it completely. My current code has a lot of
update statements like.
"update records
SQLite currently implements UPDATE by pretending it is SELECTing all the
fields, except a SET clause causes the expression(s) to be evaluated instead of
the current field value(s).
Are you using a single prepared statement and binding values (in which case,
how do you know what values to bind
5 matches
Mail list logo
