These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE Technology Lab

 
  • Topic is locked indefinitely.
 

Blueprint weirdness
Author
Previous Topic Next Topic
Trenker
#1 - 2012-02-21 20:08:31 UTC
ok, if you run this query

Quote:
SELECT tech1.typeName as tech1, tech2.typeName as tech2 FROM invblueprinttypes
JOIN invtypes as tech1 on invblueprinttypes.productTypeID = tech1.typeID
JOIN invblueprinttypes as bp_parent on invblueprinttypes.parentBlueprintTypeID = bp_parent.blueprintTypeID
JOIN invtypes as tech2 on bp_parent.productTypeID = tech2.typeID


on the current sdd, you will get something like this:

Quote:
tech1| tech2
1MN MicroWarpdrive I | 1MN MicroWarpdrive II <- that one's ok
Clone Grade Beta | Hoarder <- WTF??
Caracal | Clone Grade Gamma <- Again!?


Is that an issue of the dump or of my query? I'm using the mysql conversion of the crucible 11 dump by Jercy Fravowitz
Desmont McCallock
#2 - 2012-02-21 20:30:31 UTC
Fix your query. What exactly are you trying?
Trenker
#3 - 2012-02-22 08:44:57 UTC
I'm trying to connect tech 1 and tech 2 blueprints. I thought the parentBlueprintTypeID field in invBlueprintTypes points to its "parent", in case of a tech 2 blueprint to the tech 1 variant. The output of the query suggests it is used for something else (too).

With this query you will also get results like:
tech1 | tech2
1MN MicroWarpdrive I | 1MN MicroWarpdrive II
100MN MicroWarpdrive I | 1MN MicroWarpdrive II
100MN Afterburner II | 100MN Afterburner I

So the direct connection tech2 -> parentBlueprintTypeID = tech 1 blueprintTypeID seems to be wrong. Any hints?
Desmont McCallock
#4 - 2012-02-22 09:12:05 UTC