>Ah, I did not understand this. I ran three tests after enabling this:
>root@raspberrypi:/opt/obdpi/sql# sqlite3 trip.db 'PRAGMA journal_mode=WAL'
>wal
># time sqlite3 trip.db "delete from trip where key<=200"
>real0m0.642s
[edited]
Sqlite4
>time /root/sqlite4/sqlite4 trip.db "delete
>I'm not sure that theses tests are meaningful. First off, the conversion to
>WAL mode takes time, and that time is being included in the result.
>Secondly, WAL mode is persistent. Once it is set it stays set until it is
>changed. So you cannot turn around and run another test after setting
> On Tue, Feb 5, 2013 at 7:43 PM, Jason Gauthier <jgauth...@lastar.com>wrote:
>
>> I built the table on the same system with mysql.
>
>
> Have you tried using SQLite4 (http://www.sqlite.org/src4)? You should
> be able to download the latest check-in and type ./confi
There were a few responses to this, so I will put them all below:
Igor:
>The difference between select and delete is that the former only reads from
>the file, while the latter also writes to it. What kind of hardware does your
>>system have? Is there any reason why it may be unusually slow
Hey Everyone,
I am a fairly new user of sqlite, but not particularly new to SQL principles.
I am developing an application that will run on a low end system.
Not quite embedded, but not quite a PC. In my application, I do frequent table
deletes. My results have been poor, and I am looking
5 matches
Mail list logo
