[8.5.2] Glorp Exceptions still provide useless intormation

Hi,

I'm in the process of updating an application from VAST 8.5.0 to 8.5.2, mostly because of the improvements in Glorp.

While migration went quite smoothly (Boolean converters in DB2 work differently), I must say I am very disappointed about the exceptions. I still get calorie-free messages like "GlorpDatabaseReadError: Signal on Exception: (ExGlorpDatabaseReadError) An exception has occured" indstead of some hint of what really went wrong.
In my very first test, the problem was that VADatabaseAccessor's connection variable was nil, so I'd even be better off if I got a DoesNotUnderstand than the above-mentioned message.

The problem is that somehow the original code for display of an exception's description/messageText is wrong and doesn't fit into how exceptions work in VA Smalltalk. I hope Instantiations will clean things up for the next release.

Joachim

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/t91MFdZCgTgJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

Hi again,

If you wondered what I am complaining about in this context, you may consider taking a look at this: http://joachimtuchel.wordpress.com/2012/12/12/and-now-for-my-glorp-on-vast-error-handling-rant/

Glorp really stands in the way when it comes to finding errors.

Joachim


Am Montag, 19. November 2012 10:20:20 UTC+1 schrieb [hidden email]:

Hi,

I'm in the process of updating an application from VAST 8.5.0 to 8.5.2, mostly because of the improvements in Glorp.

While migration went quite smoothly (Boolean converters in DB2 work differently), I must say I am very disappointed about the exceptions. I still get calorie-free messages like "GlorpDatabaseReadError: Signal on Exception: (ExGlorpDatabaseReadError) An exception has occured" indstead of some hint of what really went wrong.
In my very first test, the problem was that VADatabaseAccessor's connection variable was nil, so I'd even be better off if I got a DoesNotUnderstand than the above-mentioned message.

The problem is that somehow the original code for display of an exception's description/messageText is wrong and doesn't fit into how exceptions work in VA Smalltalk. I hope Instantiations will clean things up for the next release.

Joachim

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/J9exoYFWlCsJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.