|
|
 | | Re: Unique keys for sets
|
| (...) Oya definitely. I didn't mean overwriting one of the existing ones, sorry for the confusion. There are 8 columns now, so the new one would make sense either at 1 (first), 2 (first), or 9 (last). IMHO, it makes the most sense in column 1, but I (...) (25 years ago, 28-Dec-99, to lugnet.admin.database)
| | | | | Re: Unique keys for sets
|
| Separate column please, don't make me parse it out of an existing one.. that's my opinion. As to what the keys are, I don't care, just as long as they are unique. However, as I have pontificated before, you are right. The primary key should be (...) (25 years ago, 28-Dec-99, to lugnet.admin.database)
| | | | | Re: Missing sets uploaded - 1977, 1032, 9604
|
| (...) ow, ow, bittersweet! :-) Question: Where is the number 1977 shown? (I don't see it on the scan.) How do we know that the value pack's official number is 1977, in other words? (...) The copyright on 1033 is also (c)1985 then? Do you know if (...) (25 years ago, 28-Dec-99, to lugnet.admin.database, lugnet.space, lugnet.dacta)
| | | | | Re: Unique keys for sets
|
| (...) Ok, I can stuff those in one of the columns. Are they most helpful in column 1, 2, or 9? --Todd (25 years ago, 28-Dec-99, to lugnet.admin.database)
| | | | | Re: Unique keys for sets
|
| Todd, I guess what several of us want is for those keys (regardless of whether they should be seen by humans or not) to appear in the Pause listings. Many (?) of us use the Pause listings to generate tables in our own databases and then use that for (...) (25 years ago, 28-Dec-99, to lugnet.admin.database)
|
|
