I woke up early. Not fully awake I decided to make an update to the Go4Go database. Without following my normal safe procedure I decided to work directly on the database with SQL. A minute later, I realised that I have wiped out an entire field of Go4Go database. It took me two hours to restore the data. A nice exercise for Christmas.

It's so easy to feel secure on doing "always the same"! At least you could restore it without problems... Even if it was 2 hours lost

_________________
Geek of all trades, master of none: the motto for my blog mostlymaths.net

Don't feel bad. Back in the days when I was a manager of database administration one of the people working for me needed to delete an obsolete test database. Unfortunately he the made the mistake of not checking. He was in the live production database when he executed the command. All work came to a halt while we restored from the backup and rolled in the journal file transactions. No data was lost, but over a hour's production was lost.

_________________
Still officially AGA 5d but I play so irregularly these days that I am probably only 3d or 4d over the board (but hopefully still 5d in terms of knowledge, theory and the ability to contribute).

I am reminded of a story from back in the days when a bank manager sent a plaintive letter to Byte magazine -- not much email back then -- asking, "What is the source code and how do we break it?" According to the story a database manager of a large firm was fired. Angry, he made this parting shot. He left the data in the database unchanged. He just deleted all the pointers.

_________________
The Adkins Principle:
At some point, doesn't thinking have to go on?
— Winona Adkins

Visualize whirled peas.

Everything with love. Stay safe.

If you are reading this, you have been in a coma for almost 10 years. We are trying this new technique but we don't know where this message will end up in your dream. We just hope you will somehow get it. Please wake up.

explain -.-