24.03.2015 18:42, Tim Ward wrote:

> [#] Yes, well, there's then the question about how come you're allowed
> to get a database into such an illegal state in the first place, isn't
> there.

I'd say this is what should be asked first. And it's no longer possible
starting with FB3.0.

The fix in 3.0 sounds good! - but it'll be a while for us, we're currently looking at upgrading to 2.5.

Yes, that is the first question to ask, that's the first slice of cheese: as a pilot I'm used to the Swiss cheese model for analysing cock-ups - in this case there were several holes that lined up, ie several missed opportunities to avoid the end result, and this was indeed the first.

(Our production upgrade scripts, by the way, do include deleting any pre-existing records in the table causing the problem. So assuming all the scripts are run successfully we won't have a problem with production databases, but on my dev system things had got patched here and there along the way.)

-- 
Tim Ward