|
|
 | | Re: Missing Information from Db
|
| I really need to put a post here with all the corrections I have. As I go through cataloging my sets, I check all the Pause data to see if I have any additional data (and not that I have a digital camera, I will probably take a snapshot of the box (...) (25 years ago, 30-Dec-99, to lugnet.admin.database)
| | | | | Re: Unique keys for sets
|
| The column order matters not to me, as long as it's there. Mike -- Mike Faunce mike at faunce dot com LUGNET #96 "Todd Lehman" <lehman@javanet.com> wrote in message news:3869394a.194671...net.com... (...) sense (...) sense (...) it (...) (25 years ago, 29-Dec-99, to lugnet.admin.database)
| | | | | Re: Unique keys for sets
|
| Todd Lehman <lehman@javanet.com> wrote in message news:3869394a.194671...net.com... (...) sense (...) sense (...) it (...) Todd, I think it's just the correct place to say, how about an additional column, too, if there is such an info available, or (...) (25 years ago, 29-Dec-99, to lugnet.admin.database)
| | | | | Re: Unique keys for sets
|
| lpieniazek@novera.com (Larry Pieniazek) wrote in <386943AA.328BCF33@v...ager.net>: (...) If the key you're talking about is in the form of "8880-1", then I think column 1 makes sense. I would actually be quite happy with that as a solution for a (...) (25 years ago, 29-Dec-99, to lugnet.admin.database)
| | | | | Re: Unique keys for sets
|
| (...) Not a scream, just a squeak. Consider 9, as in last and keep it last if you add something else. It has less useful info to most readers and thus should be in the region the eye reads last. (25 years ago, 28-Dec-99, to lugnet.admin.database)
| | | | | 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)
|
|
