“I decided that I wanted to compete, no matter what.”

I understand that its your sport and your back, but Im glad you didnt damage yourself further in attempting those lifts.

It’s mentally very difficult to do bed rest properly when you’ve got a competition like that looming. Good for you.

If you’re referring to the wp_1_blah, wp_2_blah stuff, that’s inherited from how Wordpress.com do it, which was merged into the mainline of Wordpress-the-software. Essentially it’s a very simple sharding scheme that serves their purposes.

Because of the nature of the stored proc compiler, the only way to make use of dynamic table/column/index/any other db object names (never an ideal practice, for this reason and others) is to string build an entire query within the code, and then EXEC it.

Unless I’m missing something, it shouldn’t really worry you. It looks messier, but it’s essentially no different to what takes place when you build your sql string in your PHP code, and then send it off to the db to compile/execute on the fly…

Out of interest, is there a reason you don’t have a separate schema for each site, rather than sharing one schema between them all?

Can queries in stored procs be made parametric in MySQL? The string concatenation approach is making me uneasy.

A little bit clumsy, passing through the varchar instead of an int, but meant I could run the script with my non-multiple site version (by passing through ” for @site_num)…