On Sun, Nov 25, 2012 at 5:46 AM, Keith Chew <keith.c...@gmail.com> wrote:
> Hi > > I found that when an update SQL is issued against a table, the WAL file > gets updated with the new record, even though the record is exactly the > same as the current record. > > Eg user table has 1 record with user_name = 'Keith'. Issuing this SQL will > increase the WAL file: > > update user set user_name='Keith'; > > Issuing it multiple times will keep increasing the size of the WAL file > each time. > > Yet, the connection.getChanges() returns 0. > > Is there a specific reason for this? Is there a way to improve this by not > inserting the record into the WAL file if the final record is not changed? > UPDATE user SET user_name='Keith' WHERE user_name!='Keith'; > > Regards > Keith > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
