Alexander Wagner a écrit : > I mean: this DB contains quite some work. There's a backup >>> of it in certain time frames (normally a yearly one at the >>> least), but if such a problem could arrise, would you >>> suggest that I dump it to pgn and reimport it? >>> >> If the base seems ok when you re-open it, I don't think it is useful. >> > > Till now it does. But tell me: is there a difference in the database > formats of 3.6.1 and 3.6.22? Could there be a cause for problems? > > I never saw anything mentioned in the changelogs and at least I was able > to open my ref-DB in scid 3.6.1 still. I feel this is a critical issue. > There is no change in DB format, but I changed block sizes. I increased their values but it had the drawback that PGN tags strip was significantly slower (I/O performance issue). So in current CVS I put old values back. This is the only important change that was made in that field, and the trickiest. But as you noticed it never prevent any Scid version from 3.6.2 to 3.6.22 to open a base generated in Scid 3.6.1. And now as the new values are back (and because I gave up the idea of handling very long games, over 64kB), there are no real changes to be feared of. This issue is annoying, and I would like to get a way to reproduce it. If I can reproduce it I am sure to be able to fix it, but if I can't reproduce it I am also sure I will not fix it.
Pascal ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Scid-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/scid-users
