Issue Details (XML | Word | Printable)

Key: CORE-2793
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Dmitry Yemanov
Reporter: Dmitry Yemanov
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.
Firebird Core

Binary representation of the backup file is inconsistent among subsequent backup/restore cycles

Created: 14/Jan/10 07:19 AM   Updated: 18/Jan/16 05:18 PM
Component/s: GBAK
Affects Version/s: 2.0.0, 1.5.4, 2.0.1, 2.0.2, 2.0.3, 1.5.5, 2.1.0, 2.0.4, 2.5 Alpha 1, 2.1.1, 2.0.5, 2.1.2, 2.5 Beta 1, 2.5 Beta 2, 2.1.3, 1.5.6, 3.0 Initial
Fix Version/s: 2.5 RC2, 2.1.4, 3.0 Alpha 1

QA Status: No test

 Description  « Hide
Reported in firebird-devel by Jean-Marc Bottura:

- I do a backup with gbak BASE.FDB -> BASE.FBK : ok

- Then a restore/backup BASE.FBK -> BASE1.FDB -> BASE1.FBK :
there are a lot of differences in the format between BASE.FBK and
BASE1.FBK ( a lot of 0x0500 added at the beginning of the FBK, the order
of the fields in the tables records is inverted, and so on ...)

- But if I do another restore/backup BASE1.FBK -> BASE2.FDB ->
BASE2.FBK : surprise ! the BASE2.FBK is exactly the same as the original
BASE.FBK (except date and time in the header)

- And if I do another restore/backup BASE2.FBK -> BASE3.FDB ->
BASE3.FBK : the BASE3.FBK is exactly the same as the BASE1.FBK

- And so on ...

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.