ita, I'll pass that question along to Steven with some others I have for him.
It's possible the site hosts will allow two domains to connect to the same table, but I don't know how sound a solution that would be.
Generally speaking, this is not allowed by webhosts.
I had other things that I was going to say but I think they've been blocked by this headache I have behind my eyes.
I think in the article they ended up with a wait_timeout of 60 seconds, not 30. (30 being the minimum they could get away with).
Which article is this, TB? I must have missed a post.
This article, ita. Rob linked to it upthread.
Yep, and after considering it while I was in the shower I think that something like five minutes would work for Buffistas. I can't believe the system leaks hundreds of connections in a few minutes, or it would be bringing the server down all the time.
Ah. Okay. I did miss that. Kristen's pitching it, so we'll see.
If Steve does wind up changing wait_timeout
, he'll need to make sure server threads get cached properly (they don't by default). This blog entry by one of Yahoo's database masters has more details.
While I'm here: Kristen, I humbly apologise for not getting back to you about CVS a while ago; my life had something of a meltdown. ita, did you get my mail a few weeks ago about CVS and the developer list? I'll take down my server if Kristen's got our needs covered.
Also, insent to ita re: developer list and SQL.
Do we have enough mySQL's to change the Random Quotes at least once a day? I like the Woodstock line, but it's not
that
good. :)
It's a matter of coding the QOTD, Wolfram. Not a top priority at the moment. :)
It's a matter of coding the QOTD, Wolfram.
Got it. Although I had to read the sentence ten times before I figured out what QOTD was, and why it needed to be coded. :)