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.
 

SDEExternalsToSql Tool (Phoebe 1.0+ compatible)

First post First post
Author
Previous Topic Next Topic
Desmont McCallock
#41 - 2014-07-27 17:27:55 UTC  |  Edited by: Desmont McCallock
I tried to make the smallest changes to the existing tables to avoid breaking changes. Therefore I kept all old columns and added new ones for those data that I found in the yaml file and was not sure where to put them.

So in the invBlueprintTypes I added the following columns:
- [duplicatingTime]
- [reverseEngineeringTime]
- [inventionTime]

In the ramTypeRequirements I added the following columns:
- [level] (I refrained from using the quantity column for this as it made more sense to add that data in there own column)
- [raceID]
- [probability]
- [consume]

I also found an inconsistency in the data parsing and I released a new beta version.
Calvin
Tritanium Forge Industries
#42 - 2014-07-27 18:02:44 UTC
Desmont McCallock wrote:
I tried to make the smallest changes to the existing tables to avoid breaking changes. Therefore I kept all old columns and added new ones for those data that I found in the yaml file and was not sure where to put them.

So in the invBlueprintTypes I added the following columns:
- [duplicatingTime]
- [reverseEngineeringTime]
- [inventionTime]

In the ramTypeRequirements I added the following columns:
- [level] (I refrained from using the quantity column for this as it made more sense to add that data in there own column)
- [raceID]
- [probability]
- [consume]

I also found an inconsistency in the data parsing and I released a new beta version.


Would I be correct in that consume is 0 if it's not consumed, and null if it is?

Can I ask how you're separating the ramTypeRequirements data from the invTypeMaterials data?

Thanks Desmont,
Desmont McCallock
#43 - 2014-07-27 18:30:56 UTC  |  Edited by: Desmont McCallock
Quote:
Would I be correct in that consume is 0 if it's not consumed, and null if it is?

Looking at the data the 'consume' attribute is only applied on datacores and if I'm not mistaken they don't get consumed anymore.
The 'Null' in the column indicates that it isn't specified.

Quote:
Can I ask how you're separating the ramTypeRequirements data from the invTypeMaterials data?

Good question, as I stumbled on that myself. invTypesMaterials is now only used to determine the reprocessed materials of an item. Everything you need for a blueprint activity is now in the ramTypeRequirements.
Calvin
Tritanium Forge Industries
#44 - 2014-07-27 18:52:52 UTC
Desmont McCallock wrote:
Quote:
Would I be correct in that consume is 0 if it's not consumed, and null if it is?

Looking at the data the 'consume' attribute is only applied on datacores and if I'm not mistaken they don't get consumed anymore.
The 'Null' in the column indicates that it isn't specified.

Quote:
Can I ask how you're separating the ramTypeRequirements data from the invTypeMaterials data?

Good question, as I stumbled on that myself. invTypesMaterials is now only used to determine the reprocessed materials of an item. Everything you need for a blueprint activity is now in the ramTypeRequirements.


Thanks for clarifying that. It does look like the 'consume = 0' characteristic is applied only to the interfaces, not datacores, which makes a bit more sense. No need to get people overly excited (-:

Thanks again for continuing to work on this Desmont!
Desmont McCallock
#45 - 2014-07-27 18:56:55 UTC
Calvin wrote:
Thanks for clarifying that. It does look like the 'consume = 0' characteristic is applied only to the interfaces, not datacores,...
Data interfaces that is, I stand corrected.
Desmont McCallock
#46 - 2014-07-27 19:01:50 UTC
OK, I will change the beta to RC, as it looks solid. I worked with it for EVEMon and things look good. So if noone else finds anything odd with it, this version will be the official release version of the tool.
Calvin
Tritanium Forge Industries
#47 - 2014-07-27 19:07:26 UTC
Desmont McCallock wrote:
OK, I will change the beta to RC, as it looks solid. I worked with it for EVEMon and things look good. So if noone else finds anything odd with it, this version will be the official release version of the tool.


Forgive me if I'm totally missing something here, but is there data here that can link a T1 BP to it's T2 invention counterpart?
Desmont McCallock
#48 - 2014-07-27 19:18:00 UTC  |  Edited by: Desmont McCallock
Yes, in ramTypeRequirements, activityID = 8, look for the requiredTypeID that is a blueprint. (i.e typeID : 879, activityID : 8, requiredTypeID : 12634). Usually it comes with a probability attribute too (in the example case it's 0.4).

Edit: I spend two weekends wrapping my head around the data in the blueprint.yaml file as it contains the combined data of two previous tables, plus new data for the Crius patch.
Calvin
Tritanium Forge Industries
#49 - 2014-07-27 19:26:45 UTC
Desmont McCallock wrote:
Yes, in ramTypeRequirements, activityID = 8, look for the requiredTypeID that is a blueprint. (i.e typeID : 879, activityID : 8, requiredTypeID : 12634). Usually it comes with a probability attribute too (in the example case it's 0.4).

Edit: I spend two weekends wrapping my head around the data in the blueprint.yaml file as it contains the combined data of two previous tables, plus new data for the Crius patch.


Ooh, I get it. Anything under activity 8 with a probability is a potential output of the invention for that BP.

Believe me, your effort is really appreciated! I tried to work with the file myself, and decided to just throw my arms up in frustration after wracking my brain on it.
Desmont McCallock
#50 - 2014-07-27 19:45:30 UTC  |  Edited by: Desmont McCallock
Anything with a probability that is not invention (activity:8) refers to reverse engineering (activity:7) which applies to typeIDs that aren't actually blueprints but create a BP due to the reverse engineering activity (and that's why those get included in the invBlueprintTypes table). Thank God I'm in this game for over 6 years now and I know all the concepts of EVE industry, otherwise I would had gone nuts.
Elisa-Verena Elestair
Garoun Investment Bank
Gallente Federation
#51 - 2014-07-29 11:22:26 UTC
Love you Desmont!

I just started in working with SQL last week at the same time of the big patch. So I was a bit frustrated to not find a way to include the blueprints into SQL. Thank you so much, I downloaded your new version right now to try it.
ItsmeHcK1
Immortalis Inc.
Shadow Cartel
#52 - 2014-07-31 21:40:54 UTC
You, sir, are a legend.
Ian Haarlem
Imbibo Ergo Sum
#53 - 2014-08-02 04:28:33 UTC
Just found this, many thanks for making it public
Cilegon
Volicorp
#54 - 2014-08-07 15:57:26 UTC  |  Edited by: Cilegon
Des, super giant thanks for this!! I'm a mssql diehard so using this to import yaml is amazing :)

one question though:

https://bitbucket.org/BattleClinic/evemon/issue/81/first-cut-of-crius-support

the talk of probablity here is something I need for invention.

I see you mention probablitly above in the ram table, but i'm not sure if it's the same thing.

for instance, i'm looking for the probablity of a tempest blueprint (-80%) which the yaml lists as .20.

any thoughts?

nvm.... i got unlazy and checked :)

select * from ramTypeRequirements where typeID = 693

this clearly shows the probablity :)
Lost Hamster
Hamster Holding Corp
#55 - 2014-08-11 21:20:20 UTC
Great tool, thanks! Just what I needed. Cool
Desmont McCallock
#56 - 2014-08-17 08:59:32 UTC
RC version for Crius has been moved to official release as no bugs or data inconsistencies have been reported.
Desmont McCallock
#57 - 2014-08-26 14:46:43 UTC
Tool still looks good for Hyperion 1.0 SDE.
Drailen
Doomheim
#58 - 2014-08-30 07:24:43 UTC
Many thanks for the tool, worked like a charm!
Desmont McCallock
#59 - 2014-09-27 07:58:38 UTC
Tool still good for Oceanus 1.0 SDE.
Hel O'Ween
Men On A Mission
#60 - 2014-11-03 17:14:13 UTC
Desmont McCallock wrote:
Tool still good for Oceanus 1.0 SDE.


Unfortunately that doesn't seem to be true for Phoebe Sad :

Importing blueprints.yaml... 99%
Ausnahmefehler: System.Exception: Key differs from blueprintTypeID
   bei EVEMon.SDEExternalsToSql.YamlToSql.Tables.Blueprints.ImportData(YamlMappingNode rNode) in e:\Projects\CSharp\BattleClinic\EVEMon\Tools\SDEExternalsToSql\YamlToSql\Tables\Blueprints.cs:line 141.
   bei EVEMon.SDEExternalsToSql.YamlToSql.Tables.Blueprints.Import() in e:\Projects\CSharp\BattleClinic\EVEMon\Tools\SDEExternalsToSql\YamlToSql\Tables\Blueprints.cs:line 92.
   bei EVEMon.SDEExternalsToSql.Program.Main() in e:\Projects\CSharp\BattleClinic\EVEMon\Tools\SDEExternalsToSql\Program.cs:line 26.

EVEWalletAware - an offline wallet manager.