> 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 PHP script to
transfer the information into my SQLite DB for analysis. I take it that
you are telling me that with the quantity of information I anticipate
writing per day - at current estimates no more than 256 bytes per page view
with around a 1000 page views per day (but growing) - I am not likely to run
into any size issues with SQLite? Like I said, as far as possible I want to
stick with SQLite.
--
View this message in context:
http://www.nabble.com/Would-SQLite-be-a-good-choice-tf4821074.html#a13793448
Sent from the SQLite mailing list archive at Nabble.com.
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
