On Monday, May 11, 2020, Dave Cramer <davecramer@postgres.rocks> wrote:
On Monday, May 11, 2020, David G. Johnston <david.g.johnston@gmail.com> wrote:
Yes, it is a bug. It should return an empty typemap
Given the code in getObject and lack of use anywhere else I’d say it should return the unsupported exception. Not reason to delay the error until later.
Actually...I’ll srick with my original thought that making it an exception now is not desirable as it could break working code (though not likely...) for no real gain.
David J.
Using it will throw an exception later in getObject()
I know...IMO that whole block in getObject should be tossed, the protected variable removed, and the getter and setter made to throw exceptions. Having the exception happen in getObject is what i’m opposed to but accept as a matter of backward compatibility.
David J.