Re: DB caching on by default?

On 19 Feb 2003, Mitch Pirtle wrote: > 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. Very good advice :-) I stopped and my problem went away! Next time I try not to be that confused :-) > 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. I had the thing sorted and it was due to silly debug message in a critical spot that lied to me horridly by producing misleading, old SQL clauses, that was not really executed at all at that time (which was because of another annoying, not so visible, bug). Anyhow. Thank for your answer. Cheers, -- --Jyry :-( C:-/ C========8-O C8-/ C:-(