More meaninful error than "Network error"

[Wowbagger]

We had a strange problem with one of our users not being able to access a shared MySQL database for the model. While the problem wasn't really EA's fault, EA didn't make the problem easy to diagnose.

The symptom was that the user could select the database, put in his credentials, successfully "Test" the connection via the test button, but when actually attempting to open the model, EA would spit out a "EA has encountered a network error and will shut down" message and die.

It turns out that the MySQL permissions for that user were screwed up, and he didn't have SELECT permissions - so EA could open the connection and "test" it, but actually USING it was broken.

The buggered permissions aren't EA's fault - but to find the problem, I had to run Wireshark and dump the communications between EA and the MySQL server.

SO:
Feature #1: If EA gets a data base error, don't just DIE - show me (or at least offer the choice to show me) the failing SQL command and the response from the server.

Feature #2: When you do the "test" button, do a bit more than just check if the connection can be created - test the various features that EA needs to work, and report on any that fail.

[Paolo F Cantoni]

Feature #1 - Yes...  EA has been pretty tight-lipped about the errors it encounters.

Feature #2 - Is outside EA's (direct) control.  It's the standard Windows OLEDB control.  The Test button is within that control - outside EA.

However, once you're back in EA, Feature #1 applies - so if they fix that, you may get your wish.  However, perhaps if (as EA opened the server connection) it tried the kinds of operations it was going to use later to might go a long way to solving the problem.

I once was in charge of testing a LONG batch app - might take 3/4 to over a day to run.   I got the developers to test some stuff on startup that they wouldn't need till over 3/4 the way in.  They complained ("but we have to test later ANYWAY!") so I told them - "if there's a problem at the beginning and no one does anything about it - there'll most likely be a problem when you test.  If you tell me the problem I might be able to fix it without a restart."

I think the same concept applies here.

You DID submit a feature/bug request?

Paolo