Discussion Forum: Thread 263251 |
|
|
| | Author: | StarBrick | Posted: | Feb 2, 2020 10:46 | Subject: | flesh2nougat: BrickStock affected? | Viewed: | 117 times | Topic: | Colors | Status: | Open | |
|
| When changes like flesh2nougat are made, what are the effects on the usage of
BrickStock for uploading, parting etc?
Any thoughts?
|
|
| | | | | |
| | | | Author: | calsbricks | Posted: | Feb 2, 2020 11:00 | Subject: | Re: flesh2nougat: BrickStock affected? | Viewed: | 58 times | Topic: | Colors | |
|
| In Colors, StarBrick writes:
| When changes like flesh2nougat are made, what are the effects on the usage of
BrickStock for uploading, parting etc?
Any thoughts?
|
None that we can see as log as you keep the database updated.
The way Bricklink was developed allowed them to simply type Nougat for Flesh
in the colours table and that filters all the way through the system for colours
and of course that is how Brickstock does it as well. We have used Brickstock
all day today and although we didn't list any Nougat's at all - there
it was in all its glory and no more flesh.
It is a different story, however on descriptions of elements - provided they
have enabled SQL Text search, they can do a search and replace for flesh etc,
but then again I think I remember someone saying there was spaghetti code in
there somewhere.
No problems with Brickstock so far, anyway.
|
|
|
| | | | | | | | | |
| | | | | | Author: | StarBrick | Posted: | Feb 2, 2020 11:40 | Subject: | Re: flesh2nougat: BrickStock affected? | Viewed: | 39 times | Topic: | Colors | |
|
| Thanks for the insights! |
|
| | | | | | | | | |
| | | | | | Author: | axaday | Posted: | Feb 2, 2020 13:31 | Subject: | Re: flesh2nougat: BrickStock affected? | Viewed: | 48 times | Topic: | Colors | |
|
| In Colors, calsbricks writes:
| The way Bricklink was developed allowed them to simply type Nougat for Flesh
in the colours table and that filters all the way through the system for colours
and of course that is how Brickstock does it as well. We have used Brickstock
all day today and although we didn't list any Nougat's at all - there
it was in all its glory and no more flesh.
|
Bricklink colors have a number associated with them that I believe is Lego's
own number. Probably Brickstock always went by the number that didn't change.
|
|
| | | | | | | | | | | | | |
| | | | | | | | Author: | SylvainLS | Posted: | Feb 2, 2020 13:46 | Subject: | Re: flesh2nougat: BrickStock affected? | Viewed: | 37 times | Topic: | Colors | |
|
| In Colors, axaday writes:
| […]
Bricklink colors have a number associated with them that I believe is Lego's
own number.
|
BL’s and TLG’s numbers are different for old colours.
| Probably Brickstock always went by the number that didn't change.
|
Simplest thing to do.
Even better: use your own IDs and have match tables so it’s easier to follow
changes (both “bla bli blo” becoming “bla bli blu” and id_01 becoming id_001),
history (keep both id_01 and id_001 pointing to your own id) and other sources.
I think that’s what BrickStock does with Part/Item IDs.
|
|
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | Author: | randyf | Posted: | Feb 2, 2020 14:18 | Subject: | Re: flesh2nougat: BrickStock affected? | Viewed: | 50 times | Topic: | Colors | |
|
| In Colors, SylvainLS writes:
| In Colors, axaday writes:
| […]
Bricklink colors have a number associated with them that I believe is Lego's
own number.
|
BL’s and TLG’s numbers are different for old colours.
|
Not just old colors. The color IDs in BrickLink are assigned as keys from the
database when new colors are added. TLG's system of numbering is completely
different.
|
| Probably Brickstock always went by the number that didn't change.
|
Simplest thing to do.
Even better: use your own IDs and have match tables so it’s easier to follow
changes (both “bla bli blo” becoming “bla bli blu” and id_01 becoming id_001),
history (keep both id_01 and id_001 pointing to your own id) and other sources.
I think that’s what BrickStock does with Part/Item IDs.
|
|
|
|
| | | | | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | Author: | SylvainLS | Posted: | Feb 2, 2020 15:27 | Subject: | Re: flesh2nougat: BrickStock affected? | Viewed: | 50 times | Topic: | Colors | |
|
| In Colors, randyf writes:
| In Colors, SylvainLS writes:
| In Colors, axaday writes:
| […]
Bricklink colors have a number associated with them that I believe is Lego's
own number.
|
BL’s and TLG’s numbers are different for old colours.
|
Not just old colors.
|
Oops, I mixed with LDraw/TLG.
LDraw now uses BL names but IDs are their own or LEGO’s.
A real mess when you manipulate the three
| The color IDs in BrickLink are assigned as keys from the
database when new colors are added. TLG's system of numbering is completely
different.
|
Yeah, I don’t know if TLG really has a system or just a couple of dice
|
|
| | | | | | | | | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | Author: | pikachu3 | Posted: | Feb 3, 2020 11:10 | Subject: | Re: flesh2nougat: BrickStock affected? | Viewed: | 44 times | Topic: | Colors | |
|
| In Colors, SylvainLS writes:
| Yeah, I don’t know if TLG really has a system or just a couple of dice
|
TLG's color IDs are vaguely chronological, but it's based on when the
color was created/added to the palette, even if they aren't actually used
in sets right away. Some colors never get used, which explains the gaps in the
IDs.
I haven't figured out the methodology behind the numbering of the first 30
or so colors, but I think it has something to do with Modulex...
Ryan
|
|
|
|
|
|