Cesar David Rodas Maldonado wrote:
I was thinking a lot in the next month in how can I do the delay insert and
I found something for do that, is basic because I don't have a lot of
knowledge, I'm just start the University.

K, I need with SQLite to select all the time as possible, and delay the
Insert, I don't care the time that took insert something. These is my
needs with SQLite. Is something Interesting on my idea? If there is one I
will share my idea.

If you're trying to save your inserts until your app has some idle time,
the best technique I can come up with is to cache those inserts in your
application. When your activity monitoring thread detects that there is
no other database activity it can fire off a process to perform the
inserts. That keeps your app very responsive to user queries.

If you find that you need a higher degree of concurrency you might
consider PostgreSQL. But you'll probably be okay with SQLite as long as
your app can find the time to run the inserts often enough.

Clay

Your all right! what i am doing right know is cache the insert query and
execute when the is not select, and that is almost working.

When i was developing my "insert delay" I thought that will be great is
SQLite support an option like MySQL (insert delay).

And i dont wanna use Postgresql, cause this is client-server, I like SQLite,
and with my "insert delay" SQLite for me is more useful than postgresql

8/5/06, Clay Dowling <clay (AT) lazarusid (DOT) comwrote:

Cesar David Rodas Maldonado wrote:
I was thinking a lot in the next month in how can I do the delay insert
and
I found something for do that, is basic because I don't have a lot of
knowledge, I'm just start the University.

K, I need with SQLite to select all the time as possible, and delay the
Insert, I don't care the time that took insert something. These is my
needs with SQLite. Is something Interesting on my idea? If there is one
I
will share my idea.

If you're trying to save your inserts until your app has some idle time,
the best technique I can come up with is to cache those inserts in your
application. When your activity monitoring thread detects that there is
no other database activity it can fire off a process to perform the
inserts. That keeps your app very responsive to user queries.

If you find that you need a higher degree of concurrency you might
consider PostgreSQL. But you'll probably be okay with SQLite as long as
your app can find the time to run the inserts often enough.

Clay