Subject:
|
Re: Add book to database?
|
Newsgroups:
|
lugnet.admin.database
|
Date:
|
Mon, 26 Jul 2010 05:51:57 GMT
|
Viewed:
|
4426 times
|
| |
|
|
In lugnet.admin.database, Joshua Delahunty wrote:
> In lugnet.admin.database, Larry Pieniazek wrote:
> > Have you considered using the ISBN? It's a lot of digits but it's a known
> > quantity.
>
> <snip>
>
> Took me awhile to get around to this.
>
> I suspected that number would be FAR too large for a key in Todd's database, and
> it turns out I was probably right. The set number entry field stops echoing
> digits after only 7. There are 13 in an ISDN.
>
> I use long integers for the set number key field in my database, so it (the
> ISDN) never would have worked there, either. The 8xxxxx numbers work there, but
> I get into trouble in another area when defining a longer key based off the set
> number (probably breaking about 3 rules you've expounding over the years, Lar
> :-))
Who me? :) Ya probably. But it is what it is.
> At one point, I think Todd was going for different values for the key versus the
> displayed set number. I doubt we'll ever see that.
>
> > (note that apparently there will be (is?) one of these for Star Wars as well:
> > http://www.amazon.com/LEGO-Brickmaster-Star-DK-Publishing/dp/0756663113/ref=pd_sim_b_6
> > coming out in November)
>
> I knew this, but Atlantis was next on the roster.
>
> > How did you handle the Star Wars book that came with an embedded minifig? ("LEGO
> > Star Wars: The Visual Dictionary", also by DK)
>
> I have this book too. It hasn't to my knowledge been entered, either.
>
> I was really hoping TLG was going to offer this items on their shopping site, so
> I could kipe their methodology here. :-/
>
> Technically, these are DK Publishing products, so tracking them in this database
> might not really be our bailiwick anyway...
>
> yeah, that's a cop-out that I don't like either. :-)
Is there any rule that could be used to assign a number that fits the size limit
but that is sure not to be a LEGO set number? All the set numbers in the DB are
nnnn-1 or nnnn-2 (rarely) right? What about the last 4 digits of the ISBN or
something and then -99 ????? This of course is the problem with using business
data for the key... what to do if the business data can't be known to be unique.
|
|
Message is in Reply To:
 | | Re: Add book to database?
|
| (...) <snip> (...) <snip> (...) <snip> Took me awhile to get around to this. I suspected that number would be FAR too large for a key in Todd's database, and it turns out I was probably right. The set number entry field stops echoing digits after (...) (14 years ago, 25-Jul-10, to lugnet.admin.database)
|
5 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
Active threads in Database
|
|
|
|
|
|
