Monday, September 5, 2011

What a great idea!

"How to log all database server errors like primary key violation error, column not found...into separate table on the same database with error message, user id, date and time. Is there any system event to log the errors?"
How to log all database server errors? by Karuppasamy, from SQL Anywhere Forum September 3, 2011

Who is Karuppasamy? He (let's go with "he" for the moment) has been a "Registered user" of the SQL Anywhere Forum since August 26 when he asked this question: SA12 server is crashing abruptly.

A week later there are still no answers to that question, and nobody's voted the question up, so there are no more reputation points for Karuppasamy beyond the single point doled out to newcomers.

Nevertheless, he hasn't lost faith in the usefulness of the forum because he's back with another question.

And judging from that new question "How to log all database server errors?" he's still working on the "crashing abruptly" problem... or maybe a new problem... whatever the case, he has just asked...

The Best Question To Come Along In A Very Long Time

That's a bold statement, and maybe you don't agree that it's even a good question since the answer is a blunt and useless "You can't."

Maybe your opinion will change if the question was edited:

Product Suggestion: SQL exception table

Please implement a table to automatically store information about all SQL exceptions; e.g. primary key violations, column not found, etc.

The table should contain the error message, user id, date and time.

"The table" should probably contain a few more things, and there should probably be discussions about turning the feature on and off, maybe even about filtering... but the bottom line is this: It would be a huge benefit to anyone developing a serious application using SQL Anywhere, and... it might not get implemented.

Why not?

Because of the UNECDIC, that's why

As you read this, a meeting of the ultra-secret United Nations Emergency Can't Do It Committee (UNECDIC) is being convened to discuss why an exception table cannot be implemented. Members of this committee include industry experts with experience in related emergencies; for example:

The good news is...

The UNECDIC has never once succeeded in keeping a good idea down, so maybe we will see an exception table in SQL Anywhere!

No comments: