Hi Lester,

Lester Caine wrote:

> masotti wrote:
>> Default transactions are IBASE_WRITE | IBASE_CONCURRENCY | IBASE_WAIT,
>> so you need to alter default transaction in client library to IBASE_READ
>> | IBASE_COMMITED | IBASE_REC_VERSION | IBASE_NO_WAIT.
>
> ADOdb default is IBASE_WAIT | IBASE_REC_VERSION | IBASE_COMMITTED
> Should I need to add IBASE_READ to that, and why not IBASE_WAIT there ?

Sorry : I missed you're using AdoDb. If most of your transactions are
read-only, why not?
I'm not sure, I'll need to refresh some theory on transactions, but if
you are reading only, what are WAITing for?
I don't remember for sure if there is a meaning for a read-only + wait
connection or they are not compatible parameters.

> I was considering adding an 'update' connection - I have used that in the past,
> but only on windows apps where the main connection may be open for some time (
> with packaged transactions ). Up until now I'd not considered it necessary since
> PHP packages up each page and should not be holding anything open? THAT is why
> the deadlock seems to be strange since the only 'update' reading pages is the
> hits counter.

Transactions are committed or rolled back at the end of the script, so
if anything else is connected to database, that seems strange to me too.
Are you monitoring database activity? Are there any other connection to
database?
Mybe you have already checked that there aren't any zombie web server
processes keeping connection/transaction alive.

As proposed from xdenser, also a insert only temporary table (on commit
retain records) that a crontab script collect and delete, or use a
separate db with EXECUTE EXTERNAL IN AUTONOMUS TRANSACTION...

Ciao.
Mimmo.