|
|
Posted by Shelly on 03/02/07 12:02
Now **that** was fast!
"Rik" <luiheidsgoeroe@hotmail.com> wrote in message
news:op.toj8ks17qnv3q9@misant...
> Shelly <sheldonlg.news@asap-consult.com> wrote:
>
>> So, my questions are:
>>
>> 1 - Other than an intermittentcy on the server, are there any ideas why
>> this
>> would happen?
>
> Do you have a very, very good reason to use mysql_pconnect()? If not, just
> use mysql_connect()....
Habit!. That is how I learned. I'll change it.
>> and much, much, more importantly:
>>
>> 2 - What would you reccommend to bulletproof this so that the customer is
>> protected and the transaction gets processed. One idea I have is rather
>> than "die", that I send an email to the seller with the insertion query
>> so
>> that it can be manually inserted later.
>
> Your database should be reachable under all circumstances... If this is
I agree.
> not the case, you might consider different hosting. Not a solution, but
> more of a temporary solution, would be to log it to a file, and run a
> cronjob that checks the file every x minutes, and tries to enter the data
> that couldn't be entered before. Do not bother your customers with extra
> actions if your script/database/server fails... Get a better
> script/database/server.
That is what I thought. It is a problem at the server end and should never
happen. So, I think for the time being I will go with my solution. Rather
than "die", I will check that $dbLogin has been set and if not set, send the
info via email to the seller for later insertion. I don't have control of
the server as it is from a hosting company and I can't set up a cron job,
and changing it right now is not practical. This was the only no connect
that I have come across from this server.
Thanks for the info and validation of my thoughts.
Shelly
Navigation:
[Reply to this message]
|