Hi there,

We have an application using sqlite, the situation is it does a lot INSERT
and DELETE,
after we bundle all INSERTs and DELETEs in transactions, INSERT becomes a
lot faster,
but DELETE seems still suffers.i have two questions.

1. Is there a way to tell sqlite to do "cheap" delete ? for example to
set certain option as compling the lib.
    by "cheap" i mean ,when it does DELETE,it does not do journal staff and
keep disk I/O at minimum.

2. The table schema is simple
    TABLE MID(id VARCHAR(8),scts VARCHAR(12),daddr VARCHAR(20))

    the scenario is it needs first select the "id" by
    select id from MID where scts= .. AND daddr=...

    after the id field is retrieved, this entry can be deleted by
    delete from MID where id=..
    or delete from MID where scts=.. AND daddr=..

     Apparently "delete" does some repeated work, ie, to locate the matching
entry from the table
     (it might be helpful to set id as PRIMARY KEY, but since insert/delete
dominates, its overhead might be higher)
     SO....
     Is there a way to tell sqlite that it can delete that entry from table
right after its id has been retrieved?


Best Regards
 Kai

Reply via email to