Thanks guys for your feedback. With regard to PEAR, I've had to patch
PEAR::DB::mysql to solve another problem I've had with the
prepared_queries field growing steadily. I'm sure this is also a problem
with the either DB subclasses. I'll post my patch to pear-dev as I don't
have a CVS account yet.
Hi Matt,
Yes, there is a risk of overflow.
From my understanding, the id is signed, so you will hit overflow at 2G
rather than 4G resources.
This applies to any/all PHP/ZE resources.
I'm not sure what happens when it overflows; it seems like the query
would fail.
You could design your
Thanks Wez,
If all that happens is the query will fail, I can live with that. It's a
simple SELECT query called over and over again. If the integer wraps
around negative, I'm guessing that would probably have undesirable
effects. If not, then I can let it run forever. What I don't want is
