[Suggestion] Number errors, giving them unique numbers

[chrisjlocke]

Following on from an error that resulted in a 'Database query error', it turns out this error occurs a lot.

Search...

Could the error messages be prefixed with a unique number? Maybe not exactly a line number, but just a unique (even sequential?) number, eg, '[413] Database query failed'
A bit like ye olden days of Basic where you got, 'Syntax error at line 657'.
Its not overly helpful as the error may still occur at a common pinchpoint, but it would still guide the person looking at the code that it was /that/ specific error the error occurred. It may be obvious (in the above error) that it could only have come from here or there, as it occurred on the front page, but sometimes if the error did say '[89] Database query failed' and you thought '89? Why would be it going there? Oh, because that part failed....' and could be a useful guide.

If agreed, I don't mind doing the numberin', as I'm useless like that.

I don't think it needs the full Microsoft 'error 0x00003bcdefffffaaa0000000' they do, but just differentiating the error strings.