SE's new home and MySQL woes
I seem to be getting the re-occuring MySQL errors that had until recently been exterminated by some session-limiting coding the admins had done. Has SE's new move fussed that all up?
It seems to be limited to the new SE++ location...
Dely Apple on