|
| | 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)
| |