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 "Mike Matrigali (JIRA)" <ji...@apache.org> on 2010/07/01 17:51:55 UTC
[jira] Resolved: (DERBY-4690) Too few arguments when generating
AM_RECORD_NOT_FOUND error
[ https://issues.apache.org/jira/browse/DERBY-4690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali resolved DERBY-4690.
-----------------------------------
Fix Version/s: 10.7.0.0
Resolution: Fixed
Committed fix to trunk. Don't think it goes to client, so minor code cleanup issue.
DERBY-4690 Too few arguments when generating AM_RECORD_NOT_FOUND error
Fixed up arguments to the AM_RECORD_NOT_FOUND exception, the page number argumen
t was missing.
m1_jdk16:133>svn commit
Sending java/engine/org/apache/derby/impl/store/access/btree/BTreeScan.java
Sending java/engine/org/apache/derby/impl/store/access/conglomerate/GenericScanController.java
Transmitting file data ..
Committed revision 959701.
> Too few arguments when generating AM_RECORD_NOT_FOUND error
> -----------------------------------------------------------
>
> Key: DERBY-4690
> URL: https://issues.apache.org/jira/browse/DERBY-4690
> Project: Derby
> Issue Type: Bug
> Components: Store
> Affects Versions: 10.7.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Mike Matrigali
> Priority: Minor
> Fix For: 10.7.0.0
>
>
> The message for AM_RECORD_NOT_FOUND has three parameters, but all the methods that generate an exception with that message, only use two of them. So the generated message ends up looking like this:
> ERROR XSAM6: Record {2} on page 7 in container 625 not found.
> whereas it should have looked like this:
> ERROR XSAM6: Record 7 on page 1 in container 625 not found.
> I don't know if these messages ever make it all the way up to the application, since they are typically caught by this code block in TableScanResultSet:
> if (se.getMessageId().equals(SQLState.AM_RECORD_NOT_FOUND))
> {
> // Somehow the row got deleted between the above
> // doesCurrentPositionQualify() call and here (one way is if
> // this scan is read uncommitted isolation level).
> return null;
> }
> But they may be logged in derby.log if the log severity level is set appropriately.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.