-
Type: Improvement
-
Status: Open
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: 3.0.2
-
Fix Version/s: QualifiedToSchedule
-
Component/s: Base Code
-
Tags:
-
Logged In as Administrator:Yes
-
Dev Mode Activated:Yes
When reproducing BDE-183, you can notice that although an explicit error message exists in server.log, no error is returned to the user launching the NXQL query:
The user gets no result, that's all.
No way for him to decipher whether there is actually no result or there is actually an error.
Expected result: when provoking an error, the user should get at the very least an error message, and if possible an explicit one.