Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <22625026.1182700345908.JavaMail.jira@brutus>
Date: Sun, 24 Jun 2007 08:52:25 -0700 (PDT)
From: =?utf-8?Q?=C3=98ystein_Gr=C3=B8vlen_=28JIRA=29?= <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-2388) DOCS - Reorder JDBC Reference
 section in Ref Manual
In-Reply-To: <1552386.1172773850908.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/DERBY-2388?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507694 ]=20

=C3=98ystein Gr=C3=B8vlen commented on DERBY-2388:
----------------------------------------

Do we really need to include a JDBC reference section?  Would it not be bet=
ter to just refer to the javadoc of the JDBC specification?  In addition, a=
 table showing which methods are supported and a section calling out any De=
rby specific issues would be needed.

If we still want to include a JDBC reference section, there should not be d=
ifferent sections for JDBC 1, 2, 3, and 4.    Everything should be put toge=
ther in one section, organized as suggested in this issue.  =20

> DOCS - Reorder JDBC Reference section in Ref Manual
> ---------------------------------------------------
>
>                 Key: DERBY-2388
>                 URL: https://issues.apache.org/jira/browse/DERBY-2388
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Laura Stewart
>            Priority: Minor
>
> The JDBC reference section isn't in alphabetical order either. It might m=
ake sense to reorder it to correspond with the javadoc (which separates int=
erfaces, classes, and exceptions into subgroups and orders them alphabetica=
lly). I'd also suggest putting java.sql.Driver.getPropertyInfo in a subtopi=
c under java.sql.Driver.=20

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.