On Fri, 27 Jan 2023 at 03:48, Steven Haigh <net...@crc.id.au> wrote: > > > On Fri, Jan 27 2023 at 10:41:02 +0800, demerphq <demer...@gmail.com> wrote: > > On Fri, 27 Jan 2023, 10:35 Steven Haigh via modperl, > <modperl@perl.apache.org> wrote: >> >> On Thu, Jan 26 2023 at 21:07:17 -0500, Perrin Harkins <phark...@gmail.com> >> wrote: >> >> Maybe you haven't committed some manual change on the server, so it isn't >> visible to other connections. >> >> >> I thought about this - but surely, restarting *everything* (db + apache + >> entire VM) would cause this to fall out. >> >> Also, when running the test script manually from the command line, surely >> that would bring up a new connection and then at least return the new data. >> >> Hell, I even went as far as to drop the table and re-create it - yet when >> querying via DBI - I still (somehow?!) get the old data :| > > > Are you absolutely certain you are in the same schema? Do you have a backup > schema hosted on the same server? > > I am pretty sure this is some kind of pebcak, but which I can't say. (No > offense intended.) > > > Oh $diety. > > You know what. I am a moron. > > I have announced that to the world. > > Your prompt actually got me to check the config of the 'adminer' frontend > I've been using - and low and behold, I've connected to a slave DB - and not > the master. > > That means all the changes I made to the data was applying just fine and > dandy - but that wasn't the master DB :) > > Ignore me. I'm the fault - and that's half a day I'll never get back hahahah > :) > > Sorry for all the noise folks :)
No problem. You aren't the first nor the last to do this. I am sure I have in the past. :-) It doesn't make you a moron at all. These things happen in a complex environment. Chalk it up to a learning experience. cheers, Yves -- perl -Mre=debug -e "/just|another|perl|hacker/"
