Thanks Martin,
alexis
Martin Engelschalk wrote:
>
> Hi Alexis,
>
> you will be ok. However, make sure to handle the SQLITE_BUSY returncode
> in your apps correctly, and keep the write-transactions short and commit
> or rollbackt them all. Based on your data, a SQLITE_BUSY will be very
> un
Hi Alexis,
you will be ok. However, make sure to handle the SQLITE_BUSY returncode
in your apps correctly, and keep the write-transactions short and commit
or rollbackt them all. Based on your data, a SQLITE_BUSY will be very
unlikely, but you have to take it into account.
See also http://www.
Hi Martin
The Java Application will do all the write. PHP will only read. (Just out of
curiosity what would the implication be if both PHP and Java did write.
Wouldn’t SQLite insure sequential write?)
As for Traffic:
Java could do 1 or 2 write's once a day.
PHP will be doing 2000 - 4000 reads a
Hi,
the important question is: What about updates to the database? Will
there be concurrent updates, or will the db be read only? Will some
processes read an others write? What amount of traffic do you expect on
the site?
See http://www.sqlite.org/faq.html#q5
Martin
alexis_ wrote:
> Hi there
Hi there,
I am at the research stage of a project i have been asked to undertake.
At the moment the O/S will be windows server 2003 and the web server IIS.
These are set and i cannot change them.
I will be using PHP to deliver the web content to users and also a Java
application will be used to
5 matches
Mail list logo