On Tue, Aug 24, 2010 at 08:38:03AM -0400, Chad Rebuck scratched on the wall:
> After changing my script to make use of querysingle instead of the
> query/fetchArray loop I was still seeing database locked notices. My
> scripts would end unexpectedly if the database lock occured at the right
>
After changing my script to make use of querysingle instead of the
query/fetchArray loop I was still seeing database locked notices. My
scripts would end unexpectedly if the database lock occured at the right
moment. Finally found the root cause of the trouble was due to not defining
a
Simon, Roger,
Thanks for the replies.
Simon, I took some of your advice and redesigned my script to use smaller
database files at least for my testing. However, I still run into this
message after starting the second process and my two processes get stuck so
no inserts/deletes occur after that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/23/2010 08:21 PM, Chad Rebuck wrote:
> I am new to databases so perhaps there is something very basic I am
> overlooking here.
You may inadvertently be causing the busy errors yourself. Have you
read this:
On 23 Aug 2010, at 3:51pm, Chad Rebuck wrote:
> I have a php script that goes though a 60,000 row table (currently a 100mb
> sqlite 3 format database that could grow to 200mb) and looks for rows that
> are missing data. Then the script retrieves data (whois queries and
> traceroute results) and
I have a php script that goes though a 60,000 row table (currently a 100mb
sqlite 3 format database that could grow to 200mb) and looks for rows that
are missing data. Then the script retrieves data (whois queries and
traceroute results) and inserts it into the table. I want to run
many
6 matches
Mail list logo