db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Levitt (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-310) Document and/or change Derby client code to match behavior with Embedded driver where possible.
Date Fri, 17 Jun 2005 04:19:49 GMT
    [ http://issues.apache.org/jira/browse/DERBY-310?page=comments#action_12313885 ] 

Jeff Levitt commented on DERBY-310:

Thanks for the feedback David,

I'll try to respond to each of your comments...

- In regards to a separate section, this document has been placed as a subsection to a larger
section called "Differences between running Derby in embedded mode and using the network server."
 There are other subsections to that main section that talk about other differences that dont
have to do with updatable result sets.  So I'm not sure what you mean by it should have its
own section.  Take a look at that area of the Server Admin Guide as it exists now:

- Of the other items linked to this issue, both were unsettled.  I wanted to at least get
the differences about updatable result sets into the docs.

- I agree that we should say something about not every difference has been identified and
that there could be more.  Perhaps I should add that to the "Differences between running Derby
in embedded mode and using the network server" page instead of this updatable result sets
differences page, since it should be a broader statement than this one subsection.  I'll make
a new patch.  Thanks!

- If Kathy has input on XA differences, I'd be happy to doc those too.  Again, if it comes
down to a timing issue in terms of whether we get some or none of these documented in 10.1,
I think it would be better to at least have added what we have than nothing at all.

- I think the formatting issues have to do with the fact that we don't have a css file to
format our output to look nicer.  Perhaps we can open a JIRA issue as an improvement and someone
could write one or find one we can use.  Such formatting issues as making the titles of tables
bold could easily be accomplished with a good css file.  I'd be happy to look into whether
the DITA toolkit has some sort of option that we can specify to put css specifications directly
into the files during transform.  I honestly haven't worked too much with them to know the
details, but I'm sure that is how its done.  I'm not optimistic that we could have something
together before 10.1 though.

-  I'll fix the header as you suggested with my new patch.  

I'll hold off on the patch for awhile to see if anyone has any other comments, suggestions,
or requests due to some of the issues David has raised.  Thanks again for the feedback!

> Document and/or change Derby client code to match behavior with Embedded driver where
> -----------------------------------------------------------------------------------------------
>          Key: DERBY-310
>          URL: http://issues.apache.org/jira/browse/DERBY-310
>      Project: Derby
>         Type: Bug
>   Components: Documentation, JDBC
>     Versions:
>     Reporter: Satheesh Bandaram
>     Priority: Minor
>  Attachments: derby310.zip
> There are some behavior differences between Derby client and embedded JDBC drivers. Change
Derby client code to match embedded behavior or document some of these differences.
> Please add any differences found to this Jira entry to keep track of known differences.
Some of the known issues are:
> * Derby-211
> * Derby-254
> * Updatable ResultSet differences.
> Kathey Marsden also started this effort to compile known differences.(http://mail-archives.apache.org/mod_mbox/db-derby-dev/200505.mbox/%3c42854697.1090403@sbcglobal.net%3e)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message