m building Flex
based products. Position is in the Washington D.C. metro area. If interested
contact [EMAIL PROTECTED]
-Original Message-
From: FredAt [mailto:[EMAIL PROTECTED]
Sent: Friday, November 16, 2007 10:17 AM
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] Would SQLite be a good ch
FredAt wrote:
>
> Thank you! I like the idea of batching the writes and dispensing with the
> intermediate flat file. However, it is not clear to me where I would run
> the dequeuer from. The only thing I can think of is running the dequeuer
> as a PHP script which I arrange to call every few
FredAt wrote:
Samuel R. Neff wrote:
You could maintain a queue in memory of all the data to be written, have
each page view queue up the new data and have a single db writer thread
that
dequeues items and writes to the db. That way you get the benefit of
writing directly to the db, but do no
Dear Fred,
I am using SQLite always in conjunction with PHP for web applications.
To give you an idea about the possibilities :
a. web application for law office :
- holds history for approx. 10.000 files with regards to accounting and
timesheets referenced to those files
- holds complete ac
FredAt <[EMAIL PROTECTED]> wrote:
> > It generally works better to append logging information to a file
> > (since this avoids the overhead of updating indices and doing
> > atomic commits) then transfering the information into an RDBMS
> > (SQLite or other) for analysis.
> >
>
> So, I guess I co
I use Sqlite to log activity in our web server. We perform the logging
asynchronously by queueing the log data and having an async process
insert it into the database so that the web connection does not block
pending completion of the insertion.
FredAt wrote:
Hello All,
I have used SQLite o
> It generally works better to append logging information to a file
> (since this avoids the overhead of updating indices and doing
> atomic commits) then transfering the information into an RDBMS
> (SQLite or other) for analysis.
>
So, I guess I could write to a flatfile and then run a daily
Samuel R. Neff wrote:
>
>
> You could maintain a queue in memory of all the data to be written, have
> each page view queue up the new data and have a single db writer thread
> that
> dequeues items and writes to the db. That way you get the benefit of
> writing directly to the db, but do not
You could maintain a queue in memory of all the data to be written, have
each page view queue up the new data and have a single db writer thread that
dequeues items and writes to the db. That way you get the benefit of
writing directly to the db, but do not have the extra overhead on each page
vi
Size should not be a problem.
Thank you very much!
--
View this message in context:
http://www.nabble.com/Would-SQLite-be-a-good-choice-tf4821074.html#a13794433
Sent from the SQLite mailing list archive at Nabble.com.
-
FredAt <[EMAIL PROTECTED]> wrote:
> Hello All,
>
> I have used SQLite off and on in Windows applications I have written and I
> really like it. However, what I am now considering doing is using a SQLite
> database to log access to one of my websites - I need to get a great deal
> more information
11 matches
Mail list logo
