> With regard to the specific scid unique game id I was thinking more of a > unique game id within the context of a scid database rather than a global id. > With that in mind, if you continue to use the game number (the relative > position in the index file) for linking between the database files and use > the unique game number just as a reference field in the display or for > exporting games then I would have thought that speed would not be such an > issue.
I agree with this idea. Since the game ids change when compacting or sorting (!) the games, I fail to see how they could be considered primary keys. And having primary keys is kinda important in database design, at least from a theorical point of view. And from a practical point of view, this seems to be what prevents Scid from implementing a linking mechanism inside annotations. We should be able to link from one game to another in the same database. More on that another time, perhaps. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
