I'm thinking using bookmarks is the best alternative. They seem to persist across base compaction, though there are probably cases where they don't.
"If the database is sorted or compacted, the bookmark details may become out of date. In this case, Scid will search the database for the best matching game (comparing player names, site, etc). If details of the bookmarked game have changed, it is possible that a different game will match the criteria better and be loaded instead. It is a good idea to re-bookmark a game if you edit its Players, Site, Result, Round or Year." You can backup and restore the plain text "bookmarks.dat" in the config directory. S. > I was wondering if there was a simple way to uniquely reference a game in a > scid database which doesn't break after compacting ? > > When I export a set of games for use in another application I would like to > keep a note of the games that I have exported so that if I need to > regenerate the list I will get the same games again from the database. I > understand that the game number cannot be relied upon because will change if > a game (before it) has been deleted and the database subsequently compacted. > > Kind regards, > Stephen Williamson ------------------------------------------------------------------------------ The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
