You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Satheesh Bandaram (JIRA)" <de...@db.apache.org> on 2005/05/23 22:22:55 UTC
[jira] Created: (DERBY-310) Document and/or change Derby client code to match behavior with Embedded driver where possible.
Document and/or change Derby client code to match behavior with Embedded driver where possible.
-----------------------------------------------------------------------------------------------
Key: DERBY-310
URL: http://issues.apache.org/jira/browse/DERBY-310
Project: Derby
Type: Bug
Components: Documentation, JDBC
Versions: 10.1.0.0
Reporter: Satheesh Bandaram
Priority: Minor
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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-310) Document and/or change Derby client
code to match behavior with Embedded driver where possible.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708292#action_12708292 ]
Dag H. Wanvik commented on DERBY-310:
-------------------------------------
+1
> Document and/or change Derby client code to match behavior with Embedded driver where possible.
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-310
> URL: https://issues.apache.org/jira/browse/DERBY-310
> Project: Derby
> Issue Type: Improvement
> Components: Documentation, JDBC
> Affects Versions: 10.1.1.0
> Reporter: Satheesh Bandaram
> Priority: Minor
>
> 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.
> This JIRA entry is a top level task for tracking these issues. Individual subtasks should be created or existing tasks linked to this Jira entry, but no specific feature content added here. Please create subtaks to this Jira entry to track any known differences documentation issues or tasks needed to investigate this issue.
> 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)
> The Derby community voted that client should match embedded where possible.
> See:
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200505.mbox/%3c4298CDDE.5070305@sbcglobal.net%3e
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-310) Document and/or change Derby client code to match behavior with Embedded driver where possible.
Posted by "Mamta A. Satoor (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-310?page=comments#action_12313892 ]
Mamta A. Satoor commented on DERBY-310:
---------------------------------------
I looked at the page with Updatable ResultSet differences and it looks good.
> Document and/or change Derby client code to match behavior with Embedded driver where possible.
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-310
> URL: http://issues.apache.org/jira/browse/DERBY-310
> Project: Derby
> Type: Bug
> Components: Documentation, JDBC
> Versions: 10.1.0.0
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [jira] Commented: (DERBY-310) Document and/or change Derby client
code to match behavior with Embedded driver where possible.
Posted by Kathey Marsden <km...@sbcglobal.net>.
Kathey Marsden (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-310?page=comments#action_12313898 ]
>
>Kathey Marsden commented on DERBY-310:
>--------------------------------------
>
>DERBY-310 should just be a place holder for this larger project of finding, documenting, or changing Client behaviour. I think we need two subtasks here now.
>1) Document updateable resultSet differences for client and embedded
>2) Document known Client/Embedded differences and future plan for client to match embedded where possible for the 10.0 release.
>
>
>
Of course should have said 10.1
>If I hear no objections, I will file these two bugs and move off the relevant content later this morning.
>
>
>
[jira] Commented: (DERBY-310) Document and/or change Derby client code to match behavior with Embedded driver where possible.
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-310?page=comments#action_12313898 ]
Kathey Marsden commented on DERBY-310:
--------------------------------------
DERBY-310 should just be a place holder for this larger project of finding, documenting, or changing Client behaviour. I think we need two subtasks here now.
1) Document updateable resultSet differences for client and embedded
2) Document known Client/Embedded differences and future plan for client to match embedded where possible for the 10.0 release.
If I hear no objections, I will file these two bugs and move off the relevant content later this morning.
> Document and/or change Derby client code to match behavior with Embedded driver where possible.
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-310
> URL: http://issues.apache.org/jira/browse/DERBY-310
> Project: Derby
> Type: Bug
> Components: Documentation, JDBC
> Versions: 10.1.0.0
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-310) Document and/or change Derby client code to match behavior with Embedded driver where possible.
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-310?page=all ]
Kathey Marsden updated DERBY-310:
---------------------------------
type: Improvement (was: Bug)
> Document and/or change Derby client code to match behavior with Embedded driver where possible.
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-310
> URL: http://issues.apache.org/jira/browse/DERBY-310
> Project: Derby
> Type: Improvement
> Components: Documentation, JDBC
> Versions: 10.1.1.0
> Reporter: Satheesh Bandaram
> Priority: Minor
>
> 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.
> This JIRA entry is a top level task for tracking these issues. Individual subtasks should be created or existing tasks linked to this Jira entry, but no specific feature content added here. Please create subtaks to this Jira entry to track any known differences documentation issues or tasks needed to investigate this issue.
> 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)
> The Derby community voted that client should match embedded where possible.
> See:
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200505.mbox/%3c4298CDDE.5070305@sbcglobal.net%3e
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-310) Document and/or change Derby client
code to match behavior with Embedded driver where possible.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-310:
--------------------------------
Description:
[NOTE: This meta-issue has been replaced by the "Bug behavior facts" flag "Embedded/client difference" DagW 2009-08-17]
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.
This JIRA entry is a top level task for tracking these issues. Individual subtasks should be created or existing tasks linked to this Jira entry, but no specific feature content added here. Please create subtaks to this Jira entry to track any known differences documentation issues or tasks needed to investigate this issue.
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)
The Derby community voted that client should match embedded where possible.
See:
http://mail-archives.apache.org/mod_mbox/db-derby-dev/200505.mbox/%3c4298CDDE.5070305@sbcglobal.net%3e
was:
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.
This JIRA entry is a top level task for tracking these issues. Individual subtasks should be created or existing tasks linked to this Jira entry, but no specific feature content added here. Please create subtaks to this Jira entry to track any known differences documentation issues or tasks needed to investigate this issue.
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)
The Derby community voted that client should match embedded where possible.
See:
http://mail-archives.apache.org/mod_mbox/db-derby-dev/200505.mbox/%3c4298CDDE.5070305@sbcglobal.net%3e
> Document and/or change Derby client code to match behavior with Embedded driver where possible.
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-310
> URL: https://issues.apache.org/jira/browse/DERBY-310
> Project: Derby
> Issue Type: Improvement
> Components: Documentation, JDBC
> Affects Versions: 10.1.1.0
> Reporter: Satheesh Bandaram
> Priority: Minor
>
> [NOTE: This meta-issue has been replaced by the "Bug behavior facts" flag "Embedded/client difference" DagW 2009-08-17]
> 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.
> This JIRA entry is a top level task for tracking these issues. Individual subtasks should be created or existing tasks linked to this Jira entry, but no specific feature content added here. Please create subtaks to this Jira entry to track any known differences documentation issues or tasks needed to investigate this issue.
> 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)
> The Derby community voted that client should match embedded where possible.
> See:
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200505.mbox/%3c4298CDDE.5070305@sbcglobal.net%3e
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-310) Document and/or change Derby client code to match behavior with Embedded driver where possible.
Posted by "David Van Couvering (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-310?page=comments#action_12313865 ]
David Van Couvering commented on DERBY-310:
-------------------------------------------
Here are my thoughts on this:
- Shouldn't this be in a separate section? There are differences between the embedded and network client beyond updatable result sets.
- There are other items linked to this JIRA id that describe other differences
- I don't think anybody has run a full test of all the embedded tests against the client to see what doesn't work. You should probably say there may be other differences that have not yet been identified
- I thought there were some differences around XA, or did Kathey and co fix all of these?
- The format that the html generator is creating is a bit klunky. These same issues existed in the error messages
document I reviewed. In particular
* The line spacing is awkward; often there is no spacing between paragraphs
* The table header should be in bold, it's hard to tell it's a table header
- The header should be "Updatable Result Sets" not "Updatable resultsets"
Thanks,
David
> Document and/or change Derby client code to match behavior with Embedded driver where possible.
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-310
> URL: http://issues.apache.org/jira/browse/DERBY-310
> Project: Derby
> Type: Bug
> Components: Documentation, JDBC
> Versions: 10.1.0.0
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-310) Document and/or change Derby client code to match behavior with Embedded driver where possible.
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-310?page=all ]
Kathey Marsden updated DERBY-310:
---------------------------------
Comment: was deleted
> Document and/or change Derby client code to match behavior with Embedded driver where possible.
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-310
> URL: http://issues.apache.org/jira/browse/DERBY-310
> Project: Derby
> Type: Bug
> Components: Documentation, JDBC
> Versions: 10.1.1.0
> Reporter: Satheesh Bandaram
> Priority: Minor
>
> 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.
> This JIRA entry is a top level task for tracking these issues. Individual subtasks should be created or existing tasks linked to this Jira entry, but no specific feature content added here. Please create subtaks to this Jira entry to track any known differences documentation issues or tasks needed to investigate this issue.
> 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)
> The Derby community voted that client should match embedded where possible.
> See:
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200505.mbox/%3c4298CDDE.5070305@sbcglobal.net%3e
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-310) Document and/or change Derby client code to match behavior with Embedded driver where possible.
Posted by "Jeff Levitt (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-310?page=comments#action_12313913 ]
Jeff Levitt commented on DERBY-310:
-----------------------------------
OK, I am going to delete the patch I create for this task and create a new one in Derby 370 with David's suggestions. That will be for updatable result sets only. I'll see if I can create patches independently for any other issues created as well.
> Document and/or change Derby client code to match behavior with Embedded driver where possible.
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-310
> URL: http://issues.apache.org/jira/browse/DERBY-310
> Project: Derby
> Type: Bug
> Components: Documentation, JDBC
> Versions: 10.1.0.0
> Reporter: Satheesh Bandaram
> Priority: Minor
>
> 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.
> This JIRA entry is a top level task for tracking these issues. Individual subtasks should be created or existing tasks linked to this Jira entry, but no specific feature content added here. Please create subtaks to this Jira entry to track any known differences documentation issues or tasks needed to investigate this issue.
> 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)
> The Derby community voted that client should match embedded where possible.
> See:
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200505.mbox/%3c4298CDDE.5070305@sbcglobal.net%3e
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-310) Document and/or change Derby client
code to match behavior with Embedded driver where possible.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707107#action_12707107 ]
Kathey Marsden commented on DERBY-310:
--------------------------------------
I think now that we have the client/embedded differences checkbox, we should just verify that the linked issues have the box checked and close this issue. Does that sound ok?
> Document and/or change Derby client code to match behavior with Embedded driver where possible.
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-310
> URL: https://issues.apache.org/jira/browse/DERBY-310
> Project: Derby
> Issue Type: Improvement
> Components: Documentation, JDBC
> Affects Versions: 10.1.1.0
> Reporter: Satheesh Bandaram
> Priority: Minor
>
> 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.
> This JIRA entry is a top level task for tracking these issues. Individual subtasks should be created or existing tasks linked to this Jira entry, but no specific feature content added here. Please create subtaks to this Jira entry to track any known differences documentation issues or tasks needed to investigate this issue.
> 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)
> The Derby community voted that client should match embedded where possible.
> See:
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200505.mbox/%3c4298CDDE.5070305@sbcglobal.net%3e
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (DERBY-310) Document and/or change Derby client
code to match behavior with Embedded driver where possible.
Posted by David Van Couvering <Da...@Sun.COM>.
Sorry, yes, I meant JEFF SAID :)
David
Jack Klebanoff wrote:
> David Van Couvering (JIRA) wrote:
>
>> [
>> http://issues.apache.org/jira/browse/DERBY-310?page=comments#action_12313949
>> ]
>> David Van Couvering commented on DERBY-310:
>> -------------------------------------------
>>
>> Sorry I didn't respond sooner..
>>
>> JACK SAID
>>
>> In regards to a separate section, this document has been placed as a
>> subsection to a larger section called [snip]
>>
>> JACK SAID
>>
>> - 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.
>>
>> [snip]
>>
>>
>>
> Did you mean "Jeff said"? I don't recall saying any of those things, nor
> do I recall any other Jacks on this list.
>
> Jack
Re: [jira] Commented: (DERBY-310) Document and/or change Derby client
code to match behavior with Embedded driver where possible.
Posted by Jack Klebanoff <kl...@sbcglobal.net>.
David Van Couvering (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-310?page=comments#action_12313949 ]
>
>David Van Couvering commented on DERBY-310:
>-------------------------------------------
>
>Sorry I didn't respond sooner..
>
>JACK SAID
>
>In regards to a separate section, this document has been placed as a subsection to a larger section called
>[snip]
>
>JACK SAID
>
>- 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.
>
>[snip]
>
>
>
Did you mean "Jeff said"? I don't recall saying any of those things, nor
do I recall any other Jacks on this list.
Jack
Re: [jira] Commented: (DERBY-310) Document and/or change Derby client
code to match behavior with Embedded driver where possible.
Posted by Kathey Marsden <km...@sbcglobal.net>.
David Van Couvering (JIRA) wrote:
>
>OK, I thought this was *the* place where differences were documented
>
>
>
I've heard no objections to keeping this bug as a top level task with
subtasks filed to keep it manageable.
We now have subtasks
http://issues.apache.org/jira/browse/DERBY-370
Document differences between Embedded and Network Server for Updatable
ResultSets functionality
http://issues.apache.org/jira/browse/DERBY-371
Document known client/embedded differences for the Version 10.1 release
David would you mind summarizing any still applicable comments from
DERBY-310 to these bugs and then deleting the comments from DERBY-310?
I think it would be great to keep DERBY-310 clean with just subtasks and
links as you suggest.
Regarding your questions about XA, there are two outstanding bugs for
client XA which would not be relevant to DERBY-310 because they are just
old fashioned bugs.
Thanks
Kathey
Re: [website] (was "Re: [jira] Commented: (DERBY-310) Document and/or
change Derby client code to match behavior with Embedded driver where possible.")
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
A quick update that I've been remiss in sending (had trouble finding
this thread).
The DITA team wants to release the Toolkit under the Apache license. As
soon as it's available under the ASL, I'll pull in the files that the
Derby docs need.
-jean
Jean T. Anderson wrote:
> I've discussed this issue with one of the Derby mentors who recommends
> that we ask the author of commonltr.css to license that particular file
> to the ASF under the Apache License.
>
> All that is needed is for the author to post a note to that effect to
> derby-dev.
>
> I'll work with Jeff on this.
>
> -jean
>
> Jean T. Anderson wrote:
>
>> I wasn't reading Jeff's email closely (my apologies).
>>
>> We aren't talking about any xsl stylesheets that DITA uses for the
>> transformation that produce the output files.
>>
>> We're talking about the cascading stylesheets used for display. They
>> don't need to be checked into svn, they just need to be accessible by
>> the html files that comprise the manuals. Jeff proposes putting the
>> stylesheet in each manual's output directory. Physical details: on
>> minotaur, this means copying the stylesheet into each
>> /www/incubator.apache.org/derby/docs/{adminguide, devguide, getstart,
>> ref, tools, tuning} subdirectory.
>>
>> There's probably a precedent for this at Apache that would confirm if
>> this is alright or not. Does anyone know for sure?
>>
>> -jean
>>
>>
>> Jean T. Anderson wrote:
>>
>>> A quick summary (Jeff, correct me if I mangled any meaning) is:
>>>
>>> - A DITA style sheet produces a pleasing format for Dreby manuals
>>> - Jeff's tweak of that style sheet improves the format even more
>>>
>>> The DITA toolkit is under the CPL license, and modifications to any
>>> of these files create derivative works under CPL. I asked
>>> legal-discuss back in March about checking files under a CPL license
>>> into the apache SVN repository, and the answer that came back was a
>>> strong "No"; I sent the status to derby-dev, see:
>>>
>>> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200503.mbox/%3c422A393D.40306@bristowhill.com%3e
>>>
>>>
>>> So, these files cannot be checked into svn.
>>>
>>> However, anyone who builds the docs is free to use that style sheet.
>>> One option might be to make the style sheet available for download
>>> from a public site outside apache. --This was an approach Ross
>>> Gardler originally proposed for a DITA plugin for forrest when he
>>> offerred to host it at Burrokeet, see:
>>> http://mail-archives.apache.org/mod_mbox/forrest-dev/200503.mbox/%3c424C7886.3030100@apache.org%3e
>>>
>>>
>>>
>>> Anyhow, let's think about the "right apache way" for us to achieve
>>> what we need -- and Derby mentors on this list should feel REALLY
>>> free to chime in with your sage advice and experience.
>>>
>>> -jean
Re: [website] (was "Re: [jira] Commented: (DERBY-310) Document and/or
change Derby client code to match behavior with Embedded driver where possible.")
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
I've discussed this issue with one of the Derby mentors who recommends
that we ask the author of commonltr.css to license that particular file
to the ASF under the Apache License.
All that is needed is for the author to post a note to that effect to
derby-dev.
I'll work with Jeff on this.
-jean
Jean T. Anderson wrote:
> I wasn't reading Jeff's email closely (my apologies).
>
> We aren't talking about any xsl stylesheets that DITA uses for the
> transformation that produce the output files.
>
> We're talking about the cascading stylesheets used for display. They
> don't need to be checked into svn, they just need to be accessible by
> the html files that comprise the manuals. Jeff proposes putting the
> stylesheet in each manual's output directory. Physical details: on
> minotaur, this means copying the stylesheet into each
> /www/incubator.apache.org/derby/docs/{adminguide, devguide, getstart,
> ref, tools, tuning} subdirectory.
>
> There's probably a precedent for this at Apache that would confirm if
> this is alright or not. Does anyone know for sure?
>
> -jean
>
>
> Jean T. Anderson wrote:
>
>> A quick summary (Jeff, correct me if I mangled any meaning) is:
>>
>> - A DITA style sheet produces a pleasing format for Dreby manuals
>> - Jeff's tweak of that style sheet improves the format even more
>>
>> The DITA toolkit is under the CPL license, and modifications to any of
>> these files create derivative works under CPL. I asked legal-discuss
>> back in March about checking files under a CPL license into the apache
>> SVN repository, and the answer that came back was a strong "No"; I
>> sent the status to derby-dev, see:
>>
>> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200503.mbox/%3c422A393D.40306@bristowhill.com%3e
>>
>>
>> So, these files cannot be checked into svn.
>>
>> However, anyone who builds the docs is free to use that style sheet.
>> One option might be to make the style sheet available for download
>> from a public site outside apache. --This was an approach Ross Gardler
>> originally proposed for a DITA plugin for forrest when he offerred to
>> host it at Burrokeet, see:
>> http://mail-archives.apache.org/mod_mbox/forrest-dev/200503.mbox/%3c424C7886.3030100@apache.org%3e
>>
>>
>>
>> Anyhow, let's think about the "right apache way" for us to achieve
>> what we need -- and Derby mentors on this list should feel REALLY free
>> to chime in with your sage advice and experience.
>>
>> -jean
>>
>>
>> Jeff Levitt wrote:
>>
>>>
>>> --- "David Van Couvering (JIRA)" wrote:
>>> <snip>
>>>
>>>> Hm. I am uncomfortable going out with the release
>>>> when the HTML is so clunky. I don't know how hard
>>>> it is to set up a css file, but it seems like if
>>>> we're trying to get people interested in using
>>>> Derby, having docs that look funky does not send out
>>>
>>>
>>>
>>> a good message to interested but hesitant new users.
>>>
>>> </snip>
>>>
>>> So this got me into sort of an investigative mode, and
>>> I took a look at the html that is output by the DITA
>>> toolkit transform. It seems there IS a css file that
>>> these files point to, but they cant find it since its
>>> not in the directory. The name of the file they all
>>> point to is commonltr.css. So, I searched through the
>>> DITA toolkit package, and I found the file in the
>>> DITA-OT1.0.1\resource\ directory. When I copied that
>>> file into the directory with my output html files and
>>> reloaded the output in my browser, suddenly everything
>>> changed formatting. The problem was it didn't change
>>> the one issue you pointed out, which was that the
>>> spacing around a table caption was non-existent, and
>>> the font of those table captions was normal text, so
>>> you couldnt distinguish it from the surrounding text. Well, after
>>> playing with the css file, I finally
>>> figured out how to modify it so that the captions are
>>> bold and are spaced with margins around them. It
>>> looks a lot better and I think you'll be satisfied
>>> with the results.
>>>
>>> So what I suggest is that we fix the website to place
>>> the commonltr.css file into each manual's html output
>>> directory. However, we should use my modified one so
>>> that the tables look better. I have attached it to
>>> this email. If this is something we can do, can a
>>> committer do this for us so that the nightly builds
>>> he change?
>>
>>
>>
>
Re: [website] (was "Re: [jira] Commented: (DERBY-310) Document and/or
change Derby client code to match behavior with Embedded driver where possible.")
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
I wasn't reading Jeff's email closely (my apologies).
We aren't talking about any xsl stylesheets that DITA uses for the
transformation that produce the output files.
We're talking about the cascading stylesheets used for display. They
don't need to be checked into svn, they just need to be accessible by
the html files that comprise the manuals. Jeff proposes putting the
stylesheet in each manual's output directory. Physical details: on
minotaur, this means copying the stylesheet into each
/www/incubator.apache.org/derby/docs/{adminguide, devguide, getstart,
ref, tools, tuning} subdirectory.
There's probably a precedent for this at Apache that would confirm if
this is alright or not. Does anyone know for sure?
-jean
Jean T. Anderson wrote:
> A quick summary (Jeff, correct me if I mangled any meaning) is:
>
> - A DITA style sheet produces a pleasing format for Dreby manuals
> - Jeff's tweak of that style sheet improves the format even more
>
> The DITA toolkit is under the CPL license, and modifications to any of
> these files create derivative works under CPL. I asked legal-discuss
> back in March about checking files under a CPL license into the apache
> SVN repository, and the answer that came back was a strong "No"; I sent
> the status to derby-dev, see:
>
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200503.mbox/%3c422A393D.40306@bristowhill.com%3e
>
>
> So, these files cannot be checked into svn.
>
> However, anyone who builds the docs is free to use that style sheet. One
> option might be to make the style sheet available for download from a
> public site outside apache. --This was an approach Ross Gardler
> originally proposed for a DITA plugin for forrest when he offerred to
> host it at Burrokeet, see:
> http://mail-archives.apache.org/mod_mbox/forrest-dev/200503.mbox/%3c424C7886.3030100@apache.org%3e
>
>
>
> Anyhow, let's think about the "right apache way" for us to achieve what
> we need -- and Derby mentors on this list should feel REALLY free to
> chime in with your sage advice and experience.
>
> -jean
>
>
> Jeff Levitt wrote:
>
>>
>> --- "David Van Couvering (JIRA)" wrote:
>> <snip>
>>
>>> Hm. I am uncomfortable going out with the release
>>> when the HTML is so clunky. I don't know how hard
>>> it is to set up a css file, but it seems like if
>>> we're trying to get people interested in using
>>> Derby, having docs that look funky does not send out
>>
>>
>> a good message to interested but hesitant new users.
>>
>> </snip>
>>
>> So this got me into sort of an investigative mode, and
>> I took a look at the html that is output by the DITA
>> toolkit transform. It seems there IS a css file that
>> these files point to, but they cant find it since its
>> not in the directory. The name of the file they all
>> point to is commonltr.css. So, I searched through the
>> DITA toolkit package, and I found the file in the
>> DITA-OT1.0.1\resource\ directory. When I copied that
>> file into the directory with my output html files and
>> reloaded the output in my browser, suddenly everything
>> changed formatting. The problem was it didn't change
>> the one issue you pointed out, which was that the
>> spacing around a table caption was non-existent, and
>> the font of those table captions was normal text, so
>> you couldnt distinguish it from the surrounding text. Well, after
>> playing with the css file, I finally
>> figured out how to modify it so that the captions are
>> bold and are spaced with margins around them. It
>> looks a lot better and I think you'll be satisfied
>> with the results.
>>
>> So what I suggest is that we fix the website to place
>> the commonltr.css file into each manual's html output
>> directory. However, we should use my modified one so
>> that the tables look better. I have attached it to
>> this email. If this is something we can do, can a
>> committer do this for us so that the nightly builds
>> he change?
>
>
Re: [website] (was "Re: [jira] Commented: (DERBY-310) Document and/or
change Derby client code to match behavior with Embedded driver where possible.")
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
A quick summary (Jeff, correct me if I mangled any meaning) is:
- A DITA style sheet produces a pleasing format for Dreby manuals
- Jeff's tweak of that style sheet improves the format even more
The DITA toolkit is under the CPL license, and modifications to any of
these files create derivative works under CPL. I asked legal-discuss
back in March about checking files under a CPL license into the apache
SVN repository, and the answer that came back was a strong "No"; I sent
the status to derby-dev, see:
http://mail-archives.apache.org/mod_mbox/db-derby-dev/200503.mbox/%3c422A393D.40306@bristowhill.com%3e
So, these files cannot be checked into svn.
However, anyone who builds the docs is free to use that style sheet. One
option might be to make the style sheet available for download from a
public site outside apache. --This was an approach Ross Gardler
originally proposed for a DITA plugin for forrest when he offerred to
host it at Burrokeet, see:
http://mail-archives.apache.org/mod_mbox/forrest-dev/200503.mbox/%3c424C7886.3030100@apache.org%3e
Anyhow, let's think about the "right apache way" for us to achieve what
we need -- and Derby mentors on this list should feel REALLY free to
chime in with your sage advice and experience.
-jean
Jeff Levitt wrote:
>
> --- "David Van Couvering (JIRA)" wrote:
> <snip>
>
>>Hm. I am uncomfortable going out with the release
>>when the HTML is so clunky. I don't know how hard
>>it is to set up a css file, but it seems like if
>>we're trying to get people interested in using
>>Derby, having docs that look funky does not send out
>
> a good message to interested but hesitant new users.
>
> </snip>
>
> So this got me into sort of an investigative mode, and
> I took a look at the html that is output by the DITA
> toolkit transform. It seems there IS a css file that
> these files point to, but they cant find it since its
> not in the directory. The name of the file they all
> point to is commonltr.css. So, I searched through the
> DITA toolkit package, and I found the file in the
> DITA-OT1.0.1\resource\ directory. When I copied that
> file into the directory with my output html files and
> reloaded the output in my browser, suddenly everything
> changed formatting. The problem was it didn't change
> the one issue you pointed out, which was that the
> spacing around a table caption was non-existent, and
> the font of those table captions was normal text, so
> you couldnt distinguish it from the surrounding text.
> Well, after playing with the css file, I finally
> figured out how to modify it so that the captions are
> bold and are spaced with margins around them. It
> looks a lot better and I think you'll be satisfied
> with the results.
>
> So what I suggest is that we fix the website to place
> the commonltr.css file into each manual's html output
> directory. However, we should use my modified one so
> that the tables look better. I have attached it to
> this email. If this is something we can do, can a
> committer do this for us so that the nightly builds
> he change?
Re: [website] (was "Re: [jira] Commented: (DERBY-310) Document and/or change Derby client code to match behavior with Embedded driver where possible.")
Posted by Jeff Levitt <de...@mylevita.com>.
Ooops, forgot to attach the modified css file! Here
it is.
[website] (was "Re: [jira] Commented: (DERBY-310) Document and/or change Derby client code to match behavior with Embedded driver where possible.")
Posted by Jeff Levitt <de...@mylevita.com>.
--- "David Van Couvering (JIRA)" wrote:
<snip>
>
> Hm. I am uncomfortable going out with the release
> when the HTML is so clunky. I don't know how hard
> it is to set up a css file, but it seems like if
> we're trying to get people interested in using
> Derby, having docs that look funky does not send out
a good message to interested but hesitant new users.
>
</snip>
So this got me into sort of an investigative mode, and
I took a look at the html that is output by the DITA
toolkit transform. It seems there IS a css file that
these files point to, but they cant find it since its
not in the directory. The name of the file they all
point to is commonltr.css. So, I searched through the
DITA toolkit package, and I found the file in the
DITA-OT1.0.1\resource\ directory. When I copied that
file into the directory with my output html files and
reloaded the output in my browser, suddenly everything
changed formatting. The problem was it didn't change
the one issue you pointed out, which was that the
spacing around a table caption was non-existent, and
the font of those table captions was normal text, so
you couldnt distinguish it from the surrounding text.
Well, after playing with the css file, I finally
figured out how to modify it so that the captions are
bold and are spaced with margins around them. It
looks a lot better and I think you'll be satisfied
with the results.
So what I suggest is that we fix the website to place
the commonltr.css file into each manual's html output
directory. However, we should use my modified one so
that the tables look better. I have attached it to
this email. If this is something we can do, can a
committer do this for us so that the nightly builds
he change?
[jira] Commented: (DERBY-310) Document and/or change Derby client code to match behavior with Embedded driver where possible.
Posted by "David Van Couvering (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-310?page=comments#action_12313949 ]
David Van Couvering commented on DERBY-310:
-------------------------------------------
Sorry I didn't respond sooner..
JACK SAID
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:
http://incubator.apache.org/derby/docs/adminguide/cadminapps.html
MY RESPONSE:
OK, I didn't know that
JACK SAID
- 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.
MY RESPONSE
OK, I thought this was *the* place where differences were documented
JACK SAID
- 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!
MY RESPONSE
Great, sounds good
JACK SAID
- 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.
MY RESPONSE
ok
JACK SAID
- 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.
MY RESPONSE
Hm. I am uncomfortable going out with the release when the HTML is so clunky. I don't know how hard it is to set up a css file, but it seems like if we're trying to get people interested in using Derby, having docs that look funky does not send out a good message to interested but hesitant new users.
JACK SAID
- I'll fix the header as you suggested with my new patch.
MY RESPONSE
ok, great
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 possible.
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-310
> URL: http://issues.apache.org/jira/browse/DERBY-310
> Project: Derby
> Type: Bug
> Components: Documentation, JDBC
> Versions: 10.1.1.0
> Reporter: Satheesh Bandaram
> Priority: Minor
>
> 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.
> This JIRA entry is a top level task for tracking these issues. Individual subtasks should be created or existing tasks linked to this Jira entry, but no specific feature content added here. Please create subtaks to this Jira entry to track any known differences documentation issues or tasks needed to investigate this issue.
> 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)
> The Derby community voted that client should match embedded where possible.
> See:
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200505.mbox/%3c4298CDDE.5070305@sbcglobal.net%3e
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-310) Document and/or change Derby client code to match behavior with Embedded driver where possible.
Posted by "Jeff Levitt (JIRA)" <de...@db.apache.org>.
[ 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:
http://incubator.apache.org/derby/docs/adminguide/cadminapps.html
- 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 possible.
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-310
> URL: http://issues.apache.org/jira/browse/DERBY-310
> Project: Derby
> Type: Bug
> Components: Documentation, JDBC
> Versions: 10.1.0.0
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-310) Document and/or change Derby client code to match behavior with Embedded driver where possible.
Posted by "Jeff Levitt (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-310?page=all ]
Jeff Levitt updated DERBY-310:
------------------------------
Attachment: derby310.zip
Attached is a zip containing a patch and sample html output for review. The patch creates a new page called "Updatable resultsets" in the admin guide under "Differences between running Derby in embedded mode and using the network server". The page includes the differences listed by Mamta. A review would be appreciated. Thanks!
> Document and/or change Derby client code to match behavior with Embedded driver where possible.
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-310
> URL: http://issues.apache.org/jira/browse/DERBY-310
> Project: Derby
> Type: Bug
> Components: Documentation, JDBC
> Versions: 10.1.0.0
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [jira] Resolved: (DERBY-310) Document and/or change Derby client
code to match behavior with Embedded driver where possible.
Posted by "Dag H. Wanvik" <Da...@Sun.COM>.
Knut Anders Hatlen <Kn...@Sun.COM> writes:
>> I agree we should close this issue, but is marking it "fixed" good?
>> Maybe "duplicate" would be better?
>
> The reason why I chose "fixed" was that I thought of this issue as one
> giant issue (the link type used for most of the issues is
> incorporates/is-part-of) that was mostly fixed, and with separate issues
> for all the remaining work. But please feel free to change it.
An alternative would be to delete those links that point to non-fixed
issues. I was worried somebody seeing this issue closed might think
all such differences had now been fixed; not a big deal, I added a
caveat in the issue description.
Dag
Re: [jira] Resolved: (DERBY-310) Document and/or change Derby client
code to match behavior with Embedded driver where possible.
Posted by Knut Anders Hatlen <Kn...@Sun.COM>.
Dag.Wanvik@Sun.COM (Dag H. Wanvik) writes:
> "Knut Anders Hatlen (JIRA)" <ji...@apache.org> writes:
>
>> [ https://issues.apache.org/jira/browse/DERBY-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>
>> Knut Anders Hatlen resolved DERBY-310.
>> --------------------------------------
>>
>> Resolution: Fixed
>
> I agree we should close this issue, but is marking it "fixed" good?
> Maybe "duplicate" would be better?
The reason why I chose "fixed" was that I thought of this issue as one
giant issue (the link type used for most of the issues is
incorporates/is-part-of) that was mostly fixed, and with separate issues
for all the remaining work. But please feel free to change it.
--
Knut Anders
Re: [jira] Resolved: (DERBY-310) Document and/or change Derby client
code to match behavior with Embedded driver where possible.
Posted by "Dag H. Wanvik" <Da...@Sun.COM>.
"Knut Anders Hatlen (JIRA)" <ji...@apache.org> writes:
> [ https://issues.apache.org/jira/browse/DERBY-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Knut Anders Hatlen resolved DERBY-310.
> --------------------------------------
>
> Resolution: Fixed
I agree we should close this issue, but is marking it "fixed" good?
Maybe "duplicate" would be better?
Dag
[jira] Resolved: (DERBY-310) Document and/or change Derby client
code to match behavior with Embedded driver where possible.
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen resolved DERBY-310.
--------------------------------------
Resolution: Fixed
All open issues linking to this issue have the Embedded/Client difference box checked. Resolving.
> Document and/or change Derby client code to match behavior with Embedded driver where possible.
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-310
> URL: https://issues.apache.org/jira/browse/DERBY-310
> Project: Derby
> Issue Type: Improvement
> Components: Documentation, JDBC
> Affects Versions: 10.1.1.0
> Reporter: Satheesh Bandaram
> Priority: Minor
>
> 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.
> This JIRA entry is a top level task for tracking these issues. Individual subtasks should be created or existing tasks linked to this Jira entry, but no specific feature content added here. Please create subtaks to this Jira entry to track any known differences documentation issues or tasks needed to investigate this issue.
> 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)
> The Derby community voted that client should match embedded where possible.
> See:
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200505.mbox/%3c4298CDDE.5070305@sbcglobal.net%3e
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-310) Document and/or change Derby client code to match behavior with Embedded driver where possible.
Posted by "David Van Couvering (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-310?page=comments#action_66109 ]
David Van Couvering commented on DERBY-310:
-------------------------------------------
I created links between this item and the bugs Satheesh referred to when he created this item. It seems to make sense that we should continue to set up links (when we find other existing items) or make subtasks for any new items. For example, perhaps all the differences identified by Mamta should be separate subtasks...
> Document and/or change Derby client code to match behavior with Embedded driver where possible.
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-310
> URL: http://issues.apache.org/jira/browse/DERBY-310
> Project: Derby
> Type: Bug
> Components: Documentation, JDBC
> Versions: 10.1.0.0
> Reporter: Satheesh Bandaram
> Priority: Minor
>
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-310) Document and/or change Derby client code to match behavior with Embedded driver where possible.
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-310?page=all ]
Kathey Marsden updated DERBY-310:
---------------------------------
Description:
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.
This JIRA entry is a top level task for tracking these issues. Individual subtasks should be created or existing tasks linked to this Jira entry, but no specific feature content added here. Please create subtaks to this Jira entry to track any known differences documentation issues or tasks needed to investigate this issue.
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)
The Derby community voted that client should match embedded where possible.
See:
http://mail-archives.apache.org/mod_mbox/db-derby-dev/200505.mbox/%3c4298CDDE.5070305@sbcglobal.net%3e
was:
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)
Environment:
> Document and/or change Derby client code to match behavior with Embedded driver where possible.
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-310
> URL: http://issues.apache.org/jira/browse/DERBY-310
> Project: Derby
> Type: Bug
> Components: Documentation, JDBC
> Versions: 10.1.0.0
> 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.
> This JIRA entry is a top level task for tracking these issues. Individual subtasks should be created or existing tasks linked to this Jira entry, but no specific feature content added here. Please create subtaks to this Jira entry to track any known differences documentation issues or tasks needed to investigate this issue.
> 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)
> The Derby community voted that client should match embedded where possible.
> See:
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200505.mbox/%3c4298CDDE.5070305@sbcglobal.net%3e
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-310) Document and/or change Derby client code to match behavior with Embedded driver where possible.
Posted by "Mamta A. Satoor (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-310?page=comments#action_66100 ]
Mamta A. Satoor commented on DERBY-310:
---------------------------------------
The functionality of updatable resultset for Network Server is similar to what Embedded Derby supports, with the exception of following differences
1)DNC requires that there be at least one column in the select list from the target table.
eg select 1, 2 from t1 for update of c11 will fail in Network Server because driver looks at both the columns in the select list and it can't determine the target table for update/delete looking at those columns' metadata. This is not required by embedded driver. There is test for this (Positive Test2 in updatableResultSet.java).
2)Embedded driver allows Statement name change when there is an open resultset on that statement object. DNC driver does not supported that. (Positive Test8a and Test8b in updatableResultSet.java )
3)(Positive Test20) Embedded driver allows updateString on SMALLINT, INTEGER, BIGINT, DECIMAL datatypes. DNC doesn't.
Embedded driver support updateBytes on CHAR, VARCHAR, LONG VARCHAR datatypes. DNC doesn't
Embedded driver support updateTime on TIMESTAMP datatypes. DNC doesn't
Embedded driver supports updateObject with null value. DNC doesn't
DNC does not support updateClob and updateBlob
> Document and/or change Derby client code to match behavior with Embedded driver where possible.
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-310
> URL: http://issues.apache.org/jira/browse/DERBY-310
> Project: Derby
> Type: Bug
> Components: Documentation, JDBC
> Versions: 10.1.0.0
> Reporter: Satheesh Bandaram
> Priority: Minor
>
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira