[jira] Updated: (DERBY-239) Need a online backup feature that does not block update operations when online backup is in progress.

[ http://issues.apache.org/jira/browse/DERBY-239?page=all ] Suresh Thalamati updated DERBY-239: --- Attachment: onlinebackup_8.diff This patch addresses the improvements suggested by Oystein in his review of the first online backup

[jira] Resolved: (DERBY-665) Remove backup(File ...) methods

[ http://issues.apache.org/jira/browse/DERBY-665?page=all ] Suresh Thalamati resolved DERBY-665: Resolution: Fixed This issue is fixed in svn commit : r372263 Remove backup(File ...) methods --- Key:

[jira] Assigned: (DERBY-665) Remove backup(File ...) methods

[ http://issues.apache.org/jira/browse/DERBY-665?page=all ] Suresh Thalamati reassigned DERBY-665: -- Assign To: Suresh Thalamati Remove backup(File ...) methods --- Key: DERBY-665 URL:

[jira] Updated: (DERBY-665) Remove backup(File ...) methods

[ http://issues.apache.org/jira/browse/DERBY-665?page=all ] Suresh Thalamati updated DERBY-665: --- Attachment: derby665.diff This patch removes the unused bacpup functions with File as paramteter, TESTS : derbyall test suite passed on Windows

[jira] Assigned: (DERBY-700) Derby does not prevent dual boot of database from different classloaders on Linux

[ http://issues.apache.org/jira/browse/DERBY-700?page=all ] Suresh Thalamati reassigned DERBY-700: -- Assign To: (was: Suresh Thalamati) Derby does not prevent dual boot of database from different classloaders on Linux

[jira] Commented: (DERBY-700) Derby does not prevent dual boot of database from different classloaders on Linux

[ http://issues.apache.org/jira/browse/DERBY-700?page=comments#action_12363492 ] Suresh Thalamati commented on DERBY-700: After doing bit of testing realized checking for OverlappingFileLockException does not work. This exception is reliable

[jira] Commented: (DERBY-700) Derby does not prevent dual boot of database from different classloaders on Linux

[ http://issues.apache.org/jira/browse/DERBY-700?page=comments#action_12363295 ] Suresh Thalamati commented on DERBY-700: Hi Kathy , I am attempting to fix this bug, just realized I may not be able to add the repro in jira into the functional

[jira] Assigned: (DERBY-700) Derby does not prevent dual boot of database from different classloaders on Linux

[ http://issues.apache.org/jira/browse/DERBY-700?page=all ] Suresh Thalamati reassigned DERBY-700: -- Assign To: Suresh Thalamati Derby does not prevent dual boot of database from different classloaders on Linux

[jira] Updated: (DERBY-239) Need a online backup feature that does not block update operations when online backup is in progress.

[ http://issues.apache.org/jira/browse/DERBY-239?page=all ] Suresh Thalamati updated DERBY-239: --- Attachment: onlinebackup_7.diff This patch addresses the issues raised by Øystein in his review of previous online backup patches 3-6. - changed the

[jira] Commented: (DERBY-810) intermittent diff for store/RecoveryAfterBackup.java test

[ http://issues.apache.org/jira/browse/DERBY-810?page=comments#action_12362682 ] Suresh Thalamati commented on DERBY-810: Difference in the output seems to be a new line. My guess is System.out and System.err (output of the printStackTrace() )

[jira] Commented: (DERBY-298) rollforward will not work correctly if the system happens to crash immediately after rollforward backup.

[ http://issues.apache.org/jira/browse/DERBY-298?page=comments#action_12361808 ] Suresh Thalamati commented on DERBY-298: Øystein , I reviewed the latest patch, it looks good. But I could not understand why you would need the following check ?

[jira] Updated: (DERBY-239) Need a online backup feature that does not block update operations when online backup is in progress.

[ http://issues.apache.org/jira/browse/DERBY-239?page=all ] Suresh Thalamati updated DERBY-239: --- Attachment: onlinebackup_6.diff This patch adds code to support online backup when jar operations are running parallel to the backup. Jar files are not

[jira] Updated: (DERBY-750) OnlineBackupTest1.java intermittently hangs

[ http://issues.apache.org/jira/browse/DERBY-750?page=all ] Suresh Thalamati updated DERBY-750: --- Attachment: obtest1.diff Thanks for posting the stack Ole. By looking at the stacks , my suspicion is backup is looking at a table that is not

[jira] Updated: (DERBY-239) Need a online backup feature that does not block update operations when online backup is in progress.

[ http://issues.apache.org/jira/browse/DERBY-239?page=all ] Suresh Thalamati updated DERBY-239: --- Attachment: obtest_customer.jar test jar file was missing from the earlier onlinebackup_6.diff patch. This jar file should be added to :

[jira] Created: (DERBY-764) java level dead lock when jar operataion are running in parallel in different transactions.

java level dead lock when jar operataion are running in parallel in different transactions. -- Key: DERBY-764 URL: http://issues.apache.org/jira/browse/DERBY-764 Project: Derby

[jira] Created: (DERBY-757) java.lang.NullPointerException can occur while scanning for global id in the transaction table under heavey load.

java.lang.NullPointerException can occur while scanning for global id in the transaction table under heavey load. -- Key: DERBY-757 URL:

[jira] Assigned: (DERBY-750) OnlineBackupTest1.java intermittently hangs

[ http://issues.apache.org/jira/browse/DERBY-750?page=all ] Suresh Thalamati reassigned DERBY-750: -- Assign To: Suresh Thalamati OnlineBackupTest1.java intermittently hangs --- Key: DERBY-750

[jira] Commented: (DERBY-750) OnlineBackupTest1.java intermittently hangs

[ http://issues.apache.org/jira/browse/DERBY-750?page=comments#action_12360233 ] Suresh Thalamati commented on DERBY-750: If some one sees this test hang, please post the stack dump. It does not reproduce on my linux/windows envirorments.

[jira] Updated: (DERBY-239) Need a online backup feature that does not block update operations when online backup is in progress.

[ http://issues.apache.org/jira/browse/DERBY-239?page=all ] Suresh Thalamati updated DERBY-239: --- Attachment: onlinebackup_4.diff This patch makes online backup call to wait/fail when unlogged operations like create index are pending. It also fixes

[jira] Updated: (DERBY-239) Need a online backup feature that does not block update operations when online backup is in progress.

[ http://issues.apache.org/jira/browse/DERBY-239?page=all ] Suresh Thalamati updated DERBY-239: --- Attachment: onlinebackup1.html minor updates to the spec: - Procedure can not be overloaded with different number of arguments in Derby. Added the

[jira] Commented: (DERBY-720) Calling SYSCS_INPLACE_COMPRESS_TABLE on a synonym or a temp table results in a NullPointerException

[ http://issues.apache.org/jira/browse/DERBY-720?page=comments#action_12358036 ] Suresh Thalamati commented on DERBY-720: derby-365 might be a duplicate of this issue. Calling SYSCS_INPLACE_COMPRESS_TABLE on a synonym or a temp table results in

[jira] Assigned: (DERBY-523) Non logged operation that starts before the log archive mode is enabled can not be recovered during rollforward recovery.

[ http://issues.apache.org/jira/browse/DERBY-523?page=all ] Suresh Thalamati reassigned DERBY-523: -- Assign To: Suresh Thalamati Non logged operation that starts before the log archive mode is enabled can not be recovered during rollforward

[jira] Updated: (DERBY-239) Need a online backup feature that does not block update operations when online backup is in progress.

[ http://issues.apache.org/jira/browse/DERBY-239?page=all ] Suresh Thalamati updated DERBY-239: --- Attachment: onlinebackup_3.diff This patch adds code to support real-time online backup with unlogged operations. A consistent backup can not be made if

[jira] Commented: (DERBY-700) Derby does not prevent dual boot of database from different classloaders on Linux

[ http://issues.apache.org/jira/browse/DERBY-700?page=comments#action_12357312 ] Suresh Thalamati commented on DERBY-700: My guess is , currently Derby seems to catch the IO exception and turn it into a readonly db , when file lock fails with

[jira] Commented: (DERBY-685) Unexpected SQL Error

[ http://issues.apache.org/jira/browse/DERBY-685?page=comments#action_12356975 ] Suresh Thalamati commented on DERBY-685: Thanks for posting the complete stack trace. By looking at the stack and related code in Logtofile.java , it appears to me the

[jira] Updated: (DERBY-239) Need a online backup feature that does not block update operations when online backup is in progress.

[ http://issues.apache.org/jira/browse/DERBY-239?page=all ] Suresh Thalamati updated DERBY-239: --- Attachment: onlinebackup_2.diff Fix to the problem found by Øystein while reviewing the previous online backup patch(online_backup1.diff). Backup of a

[jira] Commented: (DERBY-239) Need a online backup feature that does not block update operations when online backup is in progress.

[ http://issues.apache.org/jira/browse/DERBY-239?page=comments#action_12356240 ] Suresh Thalamati commented on DERBY-239: What to do if backup is started in a transaction that already has unlogged operations executed? In previous discussions

[jira] Commented: (DERBY-1) Can't create a new db on OS X

[ http://issues.apache.org/jira/browse/DERBY-1?page=comments#action_12331723 ] Suresh Thalamati commented on DERBY-1: -- Merged this fix into 10.1 client from trunk and ran all functional tests. All tests passes on jdk142/WindowsXP. I like to see

[jira] Updated: (DERBY-239) Need a online backup feature that does not block update operations when online backup is in progress.

[ http://issues.apache.org/jira/browse/DERBY-239?page=all ] Suresh Thalamati updated DERBY-239: --- Attachment: onlinebackup_1.diff This patch adds some code necessary to support real-time online backup that does not block writes when database backup

[jira] Updated: (DERBY-239) Need a online backup feature that does not block update operations when online backup is in progress.

[ http://issues.apache.org/jira/browse/DERBY-239?page=all ] Suresh Thalamati updated DERBY-239: --- Attachment: onlinebackup.html functional/design spec based on the input I got on the derby-dev list. Need a online backup feature that does not block

[jira] Commented: (DERBY-1) Can't create a new db on OS X

[ http://issues.apache.org/jira/browse/DERBY-1?page=comments#action_12331234 ] Suresh Thalamati commented on DERBY-1: -- I was hoping this issue will go away , but it seems to have appeared again in jdk1.5. Although there is a workaround by setting

[jira] Commented: (DERBY-555) Unable to restart after disk is full

[ http://issues.apache.org/jira/browse/DERBY-555?page=comments#action_12330529 ] Suresh Thalamati commented on DERBY-555: Hi Øystein, Tested your patch , it looks good .I have couple of minor questions, related to the new error message :

[jira] Created: (DERBY-577) Test harness should not change the user.dir property , it is meant for infomative purpose only.

Test harness should not change the user.dir property , it is meant for infomative purpose only. -- Key: DERBY-577 URL: http://issues.apache.org/jira/browse/DERBY-577 Project:

[jira] Commented: (DERBY-151) Thread termination - XSDG after operation is 'complete'

[ http://issues.apache.org/jira/browse/DERBY-151?page=comments#action_12329329 ] Suresh Thalamati commented on DERBY-151: derby.log occasional has more information than the above stack mentioned. In most cases , some sort of IO exception has

[jira] Commented: (DERBY-151) Thread termination - XSDG after operation is 'complete'

[ http://issues.apache.org/jira/browse/DERBY-151?page=comments#action_12329341 ] Suresh Thalamati commented on DERBY-151: Real cause for the error(ERROR XSDG1: Page Page(7,Container(0, 1088)) could not be written to disk, please check if disk is

[jira] Commented: (DERBY-555) Unable to restart after disk is full

[ http://issues.apache.org/jira/browse/DERBY-555?page=comments#action_12320936 ] Suresh Thalamati commented on DERBY-555: One case I can think of database disk is full and system is unable to create even a lock (db.lck) file also. In derby ,

[jira] Resolved: (DERBY-437) SYSCS_UTIL.SYSCS_COMPRESS_TABLE does not work on tables that are created with delimited identifier names.

[ http://issues.apache.org/jira/browse/DERBY-437?page=all ] Suresh Thalamati resolved DERBY-437: Resolution: Fixed Mike committed patch for this problem : sv n : r219207 SYSCS_UTIL.SYSCS_COMPRESS_TABLE does not work on tables that are

[jira] Created: (DERBY-521) it might be possible to preallocate the log file without blocking the log writes ..

it might be possible to preallocate the log file without blocking the log writes .. Key: DERBY-521 URL: http://issues.apache.org/jira/browse/DERBY-521 Project: Derby Type:

[jira] Created: (DERBY-523) Non logged operation that starts before the log archive mode is enabled can not be recovered during rollforward recovery.

Non logged operation that starts before the log archive mode is enabled can not be recovered during rollforward recovery. -- Key: DERBY-523 URL:

[jira] Created: (DERBY-524) weigth based page cache might improving derby throughput by keeping more heavily used pages in the page cache

weigth based page cache might improving derby throughput by keeping more heavily used pages in the page cache Key: DERBY-524 URL:

[jira] Commented: (DERBY-239) Need a online backup feature that does not block update operations when online backup is in progress.

[ http://issues.apache.org/jira/browse/DERBY-239?page=comments#action_12316434 ] Suresh Thalamati commented on DERBY-239: I think providing an online backup mechanism that does not block changes to the database when the backup is in progress will

[jira] Commented: (DERBY-426) documentation need to be modified to reflect the derby-390 fix(once it is committed) , schem , table , column names need to be in case-sensitive form.

[ http://issues.apache.org/jira/browse/DERBY-426?page=comments#action_12316168 ] Suresh Thalamati commented on DERBY-426: Changes looks good. documentation need to be modified to reflect the derby-390 fix(once it is committed) , schem , table

[jira] Commented: (DERBY-426) documentation need to be modified to reflect the derby-390 fix(once it is committed) , schem , table , column names need to be in case-sensitive form.

[ http://issues.apache.org/jira/browse/DERBY-426?page=comments#action_12315960 ] Suresh Thalamati commented on DERBY-426: Thanks for making the changes Jeff, Changes are good , except for the following minor error: Export procedures does not

[jira] Resolved: (DERBY-390) Import/export fails with table names that are quoted in SQL like import to table Order

[ http://issues.apache.org/jira/browse/DERBY-390?page=all ] Suresh Thalamati resolved DERBY-390: Fix Version: 10.1.1.0 10.2.0.0 Resolution: Fixed patch was committed to 10.1 branch wiith svn 208776 patch was committed to

[jira] Commented: (DERBY-426) documentation need to be modified to reflect the derby-390 fix(once it is committed) , schem , table , column names need to be in case-sensitive form.

[ http://issues.apache.org/jira/browse/DERBY-426?page=comments#action_12315649 ] Suresh Thalamati commented on DERBY-426: Fix for Derby-390 , that required the suggested doc change in this bug is committed to 10.1 branch. It woud be great

[jira] Assigned: (DERBY-437) SYSCS_UTIL.SYSCS_COMPRESS_TABLE does not work on tables that are created with delimited identifier names.

[ http://issues.apache.org/jira/browse/DERBY-437?page=all ] Suresh Thalamati reassigned DERBY-437: -- Assign To: Suresh Thalamati SYSCS_UTIL.SYSCS_COMPRESS_TABLE does not work on tables that are created with delimited identifier names.

[jira] Updated: (DERBY-437) SYSCS_UTIL.SYSCS_COMPRESS_TABLE does not work on tables that are created with delimited identifier names.

[ http://issues.apache.org/jira/browse/DERBY-437?page=all ] Suresh Thalamati updated DERBY-437: --- Attachment: derby437.diff Currently for compress procedure to work incase of case-sensitive table name , schema names, they needs to be passed in quotes

[jira] Commented: (DERBY-298) rollforward will not work correctly if the system happens to crash immediately after rollforward backup.

[ http://issues.apache.org/jira/browse/DERBY-298?page=comments#action_12315265 ] Suresh Thalamati commented on DERBY-298: Hi Øystein, I could not understand from the changes, If the new log file will be recognized in the following two cases:

[jira] Created: (DERBY-437) SYSCS_UTIL.SYSCS_COMPRESS_TABLE does not work on tables that are created with delimited identifier names.

SYSCS_UTIL.SYSCS_COMPRESS_TABLE does not work on tables that are created with delimited identifier names. --- Key: DERBY-437 URL:

[jira] Updated: (DERBY-390) Import/export fails with table names that are quoted in SQL like import to table Order

[ http://issues.apache.org/jira/browse/DERBY-390?page=all ] Suresh Thalamati updated DERBY-390: --- Attachment: derby390.diff patch to handle case-sensitive SQL identifiers correctly. Import/export procedure parameters for table names , schema

[jira] Commented: (DERBY-377) There is no information available in the manuals on how to upgrade a database from 10.0 to 10.1 version.

[ http://issues.apache.org/jira/browse/DERBY-377?page=comments#action_12314825 ] Suresh Thalamati commented on DERBY-377: Looks good to me.I am not sure of the following statements , In the Upgrades section , whether on upgrade from 10.0 to

[jira] Created: (DERBY-426) documentation need to be modified to reflect the derby-390 fix(once it is committed) , schem , table , column names need to be in case-sensitive form.

documentation need to be modified to reflect the derby-390 fix(once it is committed) , schem , table , column names need to be in case-sensitive form.

[jira] Commented: (DERBY-390) Import/export fails with table names that are quoted in SQL like import to table Order

[ http://issues.apache.org/jira/browse/DERBY-390?page=comments#action_12314842 ] Suresh Thalamati commented on DERBY-390: Same patch (derby390.diff) also works fine for 10.1 branch also. Ran Derbyall on 10.1 after applying the patch for a 10.1

[jira] Assigned: (DERBY-390) Import/export fails with table names that are quoted in SQL like import to table Order

[ http://issues.apache.org/jira/browse/DERBY-390?page=all ] Suresh Thalamati reassigned DERBY-390: -- Assign To: Suresh Thalamati Import/export fails with table names that are quoted in SQL like import to table Order

[jira] Commented: (DERBY-367) include documentation for SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE() in the documentation

[ http://issues.apache.org/jira/browse/DERBY-367?page=comments#action_12314634 ] Suresh Thalamati commented on DERBY-367: It might be good idea to mention about this new procedure in Server/Admin Guide: Reclaiming unused space: Chapter .

[jira] Commented: (DERBY-390) Import/export fails with table names that are quoted in SQL like import to table Order

[ http://issues.apache.org/jira/browse/DERBY-390?page=comments#action_12314415 ] Suresh Thalamati commented on DERBY-390: By looking at other system procedures and the way JDBC methods takes the table names,it looks like following the second

[jira] Created: (DERBY-390) Import/export fails with table names that are quoted in SQL like import to table Order

Import/export fails with table names that are quoted in SQL like import to table Order -- Key: DERBY-390 URL: http://issues.apache.org/jira/browse/DERBY-390 Project: Derby

[jira] Commented: (DERBY-390) Import/export fails with table names that are quoted in SQL like import to table Order

[ http://issues.apache.org/jira/browse/DERBY-390?page=comments#action_12314344 ] Suresh Thalamati commented on DERBY-390: There are two ways to fix this problem: 1) Import/Export should treat schema Names , table Names , Column Names as

[jira] Created: (DERBY-377) There is no information available in the manuals on how to upgrade a database from 10.0 to 10.1 version.

There is no information available in the manuals on how to upgrade a database from 10.0 to 10.1 version. - Key: DERBY-377 URL:

[jira] Created: (DERBY-378) support for import/export of tables with clob/blob and the other binary data types will be good addition to derby,

support for import/export of tables with clob/blob and the other binary data types will be good addition to derby, - Key: DERBY-378 URL:

[jira] Created: (DERBY-361) Unknown page format error while doing recovery after a a crash while doing in place compress.

Unknown page format error while doing recovery after a a crash while doing in place compress. --- Key: DERBY-361 URL: http://issues.apache.org/jira/browse/DERBY-361

[jira] Updated: (DERBY-361) Unknown page format error while doing recovery after a a crash while doing in place compress.

[ http://issues.apache.org/jira/browse/DERBY-361?page=all ] Suresh Thalamati updated DERBY-361: --- Attachment: wombat.jar wombat..jar - database which got unknown page format error. Unknown page format error while doing recovery after a a crash

[jira] Updated: (DERBY-361) Unknown page format error while doing recovery after a a crash while doing in place compress.

[ http://issues.apache.org/jira/browse/DERBY-361?page=all ] Suresh Thalamati updated DERBY-361: --- Attachment: derby2.log derby2.log - partial log file with log trace on. Unknown page format error while doing recovery after a a crash while

[jira] Created: (DERBY-365) inplace compress on synonym throws an assert failure. (may be it should not be allowed).

inplace compress on synonym throws an assert failure. (may be it should not be allowed). Key: DERBY-365 URL: http://issues.apache.org/jira/browse/DERBY-365 Project: Derby

[jira] Closed: (DERBY-96) partial log record writes that occur because of out-of order writes need to be handled by recovery.

[ http://issues.apache.org/jira/browse/DERBY-96?page=all ] Suresh Thalamati closed DERBY-96: - partial log record writes that occur because of out-of order writes need to be handled by recovery.

[jira] Closed: (DERBY-235) unable to create a database using a different storage factory than the one provided by default with the engine

[ http://issues.apache.org/jira/browse/DERBY-235?page=all ] Suresh Thalamati closed DERBY-235: -- unable to create a database using a different storage factory than the one provided by default with the engine

[jira] Created: (DERBY-321) ASSERT FAILED invalid space required 10012 newDataToWrite.getUsed() 10012 nextRecordOffset 189 ... on a database recoverty.

ASSERT FAILED invalid space required 10012 newDataToWrite.getUsed() 10012 nextRecordOffset 189 ... on a database recoverty. Key: DERBY-321 URL:

[jira] Resolved: (DERBY-101) Limit on Number of log that can be created should be increased (current limit is 4194303)

[ http://issues.apache.org/jira/browse/DERBY-101?page=all ] Suresh Thalamati resolved DERBY-101: Resolution: Fixed Fix Version: 10.1.0.0 chages: r170686, 178486: 178486: This fix increases the maximum possible log file number to 2^31 -1

[jira] Resolved: (DERBY-96) partial log record writes that occur because of out-of order writes need to be handled by recovery.

[ http://issues.apache.org/jira/browse/DERBY-96?page=all ] Suresh Thalamati resolved DERBY-96: --- Resolution: Fixed Fix Version: 10.1.0.0 Following changes fixed this problem: r178494 : small fix to make sure that log buffers are switched are

[jira] Assigned: (DERBY-239) Need a online backup feature that does not block update operations when online backup is in progress.

[ http://issues.apache.org/jira/browse/DERBY-239?page=all ] Suresh Thalamati reassigned DERBY-239: -- Assign To: Suresh Thalamati Need a online backup feature that does not block update operations when online backup is in progress.

[jira] Created: (DERBY-298) rollforward will not work correctly if the system happens to crash immediately after rollforward backup.

rollforward will not work correctly if the system happens to crash immediately after rollforward backup. - Key: DERBY-298 URL: http://issues.apache.org/jira/browse/DERBY-298

[jira] Resolved: (DERBY-235) unable to create a database using a different storage factory than the one provided by default with the engine

[ http://issues.apache.org/jira/browse/DERBY-235?page=all ] Suresh Thalamati resolved DERBY-235: Resolution: Fixed Fix Version: 10.1.0.0 patch is commiteed for this problem with svn 165645 unable to create a database using a different

[jira] Created: (DERBY-235) unable to create a database using a different storage factory than the one provided by default with the engine

unable to create a database using a different storage factory than the one provided by default with the engine -- Key: DERBY-235 URL:

[jira] Commented: (DERBY-96) partial log record writes that occur because of out-of order writes need to be handled by recovery.

[ http://issues.apache.org/jira/browse/DERBY-96?page=comments#action_59041 ] Suresh Thalamati commented on DERBY-96: --- Conclusion was to solve this problem by writing a checksum log record before writing the log buffer and verify the checksum

[jira] Commented: (DERBY-133) Autocommit turned false and rollbacks

[ http://issues.apache.org/jira/browse/DERBY-133?page=comments#action_58066 ] Suresh Thalamati commented on DERBY-133: I don't think whole transaction should be rolled back , if an insert fails with foreign key constraint violation only the

[jira] Resolved: (DERBY-94) Lock not being released properly, possibly related to occurence of lock escalation

[ http://issues.apache.org/jira/browse/DERBY-94?page=history ] Suresh Thalamati resolved DERBY-94: --- Resolution: Fixed This issue has been fixed with SVN COMMIT r123267. Lock not being released properly, possibly related to occurence of lock

[jira] Assigned: (DERBY-96) partial log record writes that occur because of out-of order writes need to be handled by recovery.

[ http://nagoya.apache.org/jira/browse/DERBY-96?page=history ] Suresh Thalamati reassigned DERBY-96: - Assign To: Suresh Thalamati partial log record writes that occur because of out-of order writes need to be handled by recovery.

[jira] Created: (DERBY-96) partial log record writes that occur because of out-of order writes need to be handled by recovery.

partial log record writes that occur because of out-of order writes need to be handled by recovery. --- Key: DERBY-96 URL: http://nagoya.apache.org/jira/browse/DERBY-96 Project:

[jira] Commented: (DERBY-96) partial log record writes that occur because of out-of order writes need to be handled by recovery.

[ http://nagoya.apache.org/jira/browse/DERBY-96?page=comments#action_56482 ] Suresh Thalamati commented on DERBY-96: --- Some thoughts on how this problem could be solved: To identify the partial writes, some form of checksum has to be added to the

<    1   2   3