|
[
Permlink
| « Hide
]
David Van Couvering added a comment - 24/May/05 06:32 AM
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...
Derby-310 is trying to compile all list of known issues.
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!
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 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! I looked at the page with Updatable ResultSet differences and it looks good.
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.
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! Linking this to
isReadOnly() and possibly isWriteOnly() don't match behavior between DerbyClient and embedded.
Linking Derby-911(Connection.setReadOnly is a no-op in Network Client but works fine with embedded driver) to Derby-310(Document and/or change Derby client code to match behavior with Embedded driver where possible.)
Linked
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?
All open issues linking to this issue have the Embedded/Client difference box checked. Resolving.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Resolved
Minor
Document and/or change Derby client code to match behavior with Embedded driver where possible.
