db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vemund Ostgaard <Vemund.Ostga...@Sun.COM>
Subject Re: possible JDBC 4 EOD bug??
Date Fri, 15 Sep 2006 15:20:35 GMT
Daniel John Debrunner wrote:

>Vemund Ostgaard wrote:
>
>  
>
>>Daniel John Debrunner wrote:
>>    
>>
>
>  
>
>>>If my select returns a column called 'NAME' then it does not map to the
>>>JavaBean property called 'name'. Instead the name of the column needs to
>>>map to the name of the private field, 'myName'. Then the field is set
>>>correctly but the setter is never used. Is this a bug, it seems like it?
>>> 
>>>
>>>      
>>>
>>If I understand you correctly, I believe it is a known bug that I
>>stumbled on myself a while ago. I thought it had been fixed in one of
>>the latest Mustang builds but I haven't verified it myself. Which build
>>have you been using?
>>    
>>
>
>Thanks, the description was a bit rushed because I had ony a little time
>before I needed to leave and I wanted to get the question out there.
>Do you have the bug number for the issue?
>  
>
My understanding was that this would be fixed by 6460994, which went 
into b97.

>I'm using b98.
>  
>
That should indicate that it didn't get fixed as part of that bug report.

Vemund

Mime
View raw message