Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 2 of 2 total |
VerifyTable and RepairTable return incorrect results after CopyTable |
Wed, Jan 28 2009 1:49 AM | Permanent Link |
Marilyn Fleming | dbisam 4.27r3, Delphi 2007
When copying a table with blob fields, VerifyTable and RepairTable return False on a copied table. Attachments: dbisambug.zip |
Sat, Feb 7 2009 2:11 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Marilyn,
<< When copying a table with blob fields, VerifyTable and RepairTable return False on a copied table. >> Please post any binary attachments in the Binaries newsgroup only. As for the issue, there's an issue with the source table that is only being exposed when the table records are copied over to a new copy of the table. For example, calling OptimizeTable on the table, and then repairing the table, will result in the same issue. OptimizeTable, CopyTable, etc. all copy over the existing row checksums, so they do not generate new checksums. However, they do copy over the data field-by-field and record-by-record, which is why these processes expose the difference between the actual record data and the checksum that is stored for the record. If the table is particularly old, then the problem could have been originally caused by this: http://www.elevatesoft.com/incident?action=viewrep&category=dbisam&release=4.07&type=f&incident=1744 -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Tuesday, April 30, 2024 at 03:55 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |