[
https://issues.apache.org/jira/browse/DERBY-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828157#action_12828157
]
Knut Anders Hatlen commented on DERBY-2286:
-------------------------------------------
The failing call to UpdateOperation.writeOptionalDataToBuffer() has the
following rather cryptic comment:
// RESOLVE SRW-DJD/YYZ
Does anyone know how to decipher that?
I agree with Suresh's observation that it looks like NoSpaceOnPage is supposed
to be caught and recovered from. Perhaps it would be better if it didn't extend
StandardException, so that all callers would have to handle it explicitly. When
it extends StandardException, it's easier that it falls through the cracks and
gets handled by the default StandardException handler, which eventually returns
the error to the user.
> Exception NoSpaceOnPage does not provide SQLState or exception text
> -------------------------------------------------------------------
>
> Key: DERBY-2286
> URL: https://issues.apache.org/jira/browse/DERBY-2286
> Project: Derby
> Issue Type: Bug
> Components: Store
> Affects Versions: 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.5.3.0
> Reporter: Andrew McIntyre
> Priority: Minor
> Attachments: NoSpaceBug.java
>
>
> Originally reported on the derby-user list in this post:
> http://mail-archives.apache.org/mod_mbox/db-derby-user/200701.mbox/%[email protected]%3e
> The user encountered an impl.store.raw.data.NoSpaceOnPage exception during a
> batch update. The exception currently does not provide a SQLState or
> exception text explaining the cause of the error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
