Hi everyone, sorry first and foremost for the disruption that’s been caused here (and thanks everyone for your patience and especially to Peter, Bernhard and everyone else who took the time to help other users here).
This is indeed a bug in 3.0.2 that affects anyone with a database table prefix other than the default of wp_ – we’re quite literally working on a fix for this and hope to roll it out as soon as possible.
Once again, our apologies for this – it goes without saying it absolutely wasn’t our intention for this to happen – and we hope to get a solution out ASAP.