db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Van Couvering <David.Vancouver...@Sun.COM>
Subject Re: [jira] Updated: (DERBY-1566) Document SQLStates in 10.2
Date Tue, 29 Aug 2006 17:56:03 GMT
It's not the severity code.  What you are seeing are the SQL State 
classes (the first two characters of the SQL State) that are new in 
10.2.  Most of these are related to DRDA, as part of the client work.

I will attach to the JIRA a version of the ErrorMessageGenerator which 
added descriptions for these new SQL State classes.  I was able to get a 
clean run without any warnings.

David

Jean T. Anderson wrote:
> David Van Couvering wrote:
>> Guess you gave up on me Jean :)  This was something I was going to work
>> on this week.  We should figure out how we want to collaborate.  I do
>> have to admit I am majorly swamped with some other projects right now,
>> so if you have the time and inclination...
> 
> I have a little time and inclination this week.
> 
>> Anyway, let me know if you need assistance, this was something I had
>> committed to getting done.
>>
>> Also, I am thinking this should be checked in somewhere (I was thinking
>> in the derbyBuild directory), compiled as part of the build, and run by
>> the release manager at appropriate points in time.  Unless you have
>> thoughts about how to automate this.  The problem is it is Java source
>> code generating DITA files, so it semantically crosses two independent
>> svn repositories...
> 
> Since the dita source that gets output needs attention before it can
> work, I think it's best off as a standalone app right now.
> 
> In fact, yesterday I was running it standalone -- in a shell set for the
> 10.1 classpath, so I'll upload a new html file.
> 
> With a 10.2 classpath set, it spits out many more of those "unable to
> determine code" errors:
> 
> Unable to determine code for SQL State 0A000 (repeats many times)
> Unable to determine code for SQL State 2D521 (repeats)
> Unable to determine code for SQL State 39004
> Unable to determine code for SQL State 57017
> Unable to determine code for SQL State 58009 (repeats many times)
> Unable to determine code for SQL State 58010
> Unable to determine code for SQL State 58014
> Unable to determine code for SQL State 58015
> Unable to determine code for SQL State 58016
> Unable to determine code for SQL State 58017
> Unable to determine code for SQL State X0A00
> Unable to determine code for SQL State XN001
> Unable to determine code for SQL State XN008
> Unable to determine code for SQL State XN009
> Unable to determine code for SQL State XN010
> Unable to determine code for SQL State XN011
> Unable to determine code for SQL State XN012
> Unable to determine code for SQL State XN013
> Unable to determine code for SQL State XN014
> Unable to determine code for SQL State XN015
> Unable to determine code for SQL State XN016
> Unable to determine code for SQL State XN017
> Unable to determine code for SQL State XN018
> Unable to determine code for SQL State XN019
> 
> I haven't dug into this part of your app yet -- do you recall if it's
> just the severity code it's complaining about? If you don't remember, no
> worries, I'll poke at it some more later today.
> 
>  -jean
> 
> 
>> David
>>
>> Jean T. Anderson (JIRA) wrote:
>>
>>>      [ http://issues.apache.org/jira/browse/DERBY-1566?page=all ]
>>>
>>> Jean T. Anderson updated DERBY-1566:
>>> ------------------------------------
>>>
>>>     Attachment: ErrorMessageGenerator.java
>>>                 rrefexcept71493.html
>>>
>>> ErrorMessageGenerator.java is a copy of DERBY-296's app modified as
>>> follows:
>>>
>>> 1) Replaced the "-//IBM//DTD DITA Reference//EN" with ""-//OASIS//DTD
>>> DITA Reference//EN"
>>>
>>> 2) Some tags needed a space .  For example, the 'xml' in this tag:
>>> <reference id="rrefexcept13113"xml:lang="en-us">
>>> needed a space before the 'xml' so xml parsing would succeed:
>>> <reference id="rrefexcept13113" xml:lang="en-us">
>>>
>>> 3) Needed some close tags for DITA processing to succeed.
>>>
>>> Running it outputs two errors:
>>> $ java ErrorMessageGenerator
>>> Unable to determine code for SQL State 0A000
>>> Unable to determine code for SQL State 39004
>>>
>>> The DITA source that it generates needs one manual change. The message
>>> for 42Y04 has '<' and '>' in the message.
>>> Change this: <full java path>.<method name>
>>> To this:     &lt;full java path&gt;.&lt;method name&gt;
>>>
>>> rrefexcept71493.html shows sample output.
>>>
>>>
>>>
>>>> Document SQLStates in 10.2
>>>> --------------------------
>>>>
>>>>                 Key: DERBY-1566
>>>>                 URL: http://issues.apache.org/jira/browse/DERBY-1566
>>>>             Project: Derby
>>>>          Issue Type: Improvement
>>>>          Components: Documentation
>>>>    Affects Versions: 10.2.1.0
>>>>            Reporter: Rick Hillegas
>>>>         Assigned To: David Van Couvering
>>>>             Fix For: 10.2.1.0
>>>>
>>>>         Attachments: ErrorMessageGenerator.java, rrefexcept71493.html
>>>>
>>>>
>>>> We need to update the Reference Guide to document the current list of
>>>> SQLStates. This list goes into
>>>> Reference Guide
>>>>   Derby exception messages and SQL states
>>>>     SQLState and error message reference
>>>> The tool mentioned in DERBY-296 may be useful.
>>>
> 

Mime
View raw message