Re: DB caching on by default?
| From: | Mitch Pirtle | Date: | Wed, 19 Feb 2003 10:46:34 +0000 |
| Subject: | Re: DB caching on by default? | ||
| References: | 1 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-3826@lists.php.net to get a copy of this message | ||
On Tue, 2003-02-18 at 16:20, Jyry Kuukkanen wrote:
> It worked fine using native PostgreSQL/PHP funcs, so I though there might
> be some caching turned on by default using PEAR interface.
>
> The similar problem appears with INSERT and it buzzles me pretty much.
First, whatever you do, don't be buzzled.
I'll wager that you need a commit for this to work. The built-in php
functions have implicit commits, IIRC.
Can you send the code that performs the SQL? I'm just guessing right
now, but could probably help better if I knew how you were preparing and
executing the code.
-- Mitch
Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc
Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc