[
https://issues.apache.org/jira/browse/DERBY-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505187
]
Øystein Grøvlen commented on DERBY-2729:
----------------------------------------
Some comments on the release notes:
- The summary should be a one-liner
- The bold text for embedded driver and client is confusing since they
look similar to the section headings. I suggest not using bold, but
plain text with a succeeding colon, instead.
- Since the behavior is now the same for both client and embedded, I
do not think it is necessary to dwell with previous differences.
That would make things a bit simpler. E.g., instead of mentioning
that the change is only for short lobs, you can just say that it now
holds for all Lobs. That way, I think you do not really need to
write separate statements for client and embedded.
- For the 'Application Changes Required' section, you can refer to the
release note for the locator-based implementation (DERBY-208) for a
discussion on the effects of changing the transaction life span.
- For the first paragraph, I think it is sufficient to say:
"A Blob or Clob object is no longer valid after the termination
(commit or rollback) of the transaction it were created in."
Since transaction cannot live beyond a connection this should cover
that case, but I guess it does not harm to state that explicitly. I
do not think it is necessary to discuss implicit or explicit
commits/rollbacks here.
> temporary lob file should be cleaned when the transaction or connection is no
> longer valid.
> -------------------------------------------------------------------------------------------
>
> Key: DERBY-2729
> URL: https://issues.apache.org/jira/browse/DERBY-2729
> Project: Derby
> Issue Type: Bug
> Reporter: Anurag Shekhar
> Assignee: Anurag Shekhar
> Fix For: 10.3.0.0
>
> Attachments: derby-2729.diff, releaseNote.html
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
