 | | Re: Unique keys for sets
|
|
(...) No, the primary keys in that DB haven't changed since they were first created in April of 1998. When the DB is reborn out of its current form and into its new form, the old keys will be obsolete, but there will be a backward compatible (...) (25 years ago, 28-Dec-99, to lugnet.admin.database)
|
| |
| | Re: Unique keys for sets
|
|
A few minutes ago, I posted: (...) But... hm. A possible problem with documenting the key is that the unique key used in the Pause database appears to change over time. If TLC were to come out with another set numbered 8880, what would the keys be (...) (25 years ago, 27-Dec-99, to lugnet.admin.database)
|
| |
| | Unique keys for sets
|
|
Would it possible and reasonable to add a unique key to the Pause database setlists? In effect, to add another column to: (URL) the related lists. I've got a fairly hairy spreadsheet that I use to keep track of my sets. I use the Pause database as a (...) (25 years ago, 27-Dec-99, to lugnet.admin.database)
|
| |
| | Re: Missing Information from Db
|
|
(...) Thanks, Craig! --Todd (25 years ago, 21-Dec-99, to lugnet.admin.database)
|
| |
| | Missing Information from Db
|
|
Hi all, I was creating a local db of my collection (which included adding all set information since 1980...right now I don't plan on collecting anything earlier than that) and ran across some missing piece counts that can be found in the current (...) (25 years ago, 21-Dec-99, to lugnet.admin.database)
|
