EVE Technology Lab

Does anyone know of a good way of storing eve fittings in mysql that doesn't break the normalisation rules?

I'm making a site that stores alliance fittings and have one table that stores ship details (name, type, tech level etc) and another table that stores module information (name, price etc). What is a good way of then creating a fitting table without having to have a table for each class of ship or many null values?

If you do end up using ship DNA, take a look at https://github.com/fuzzysteve/Ship.js Might be of interest.

If you're /really/ interested in a normalised form of storage (and want to be able to search for all ships with a particular module, which is the only reason to break it out into a database understandable form) something like:


Fitting table
--- id, Ship type, name, other meta data you might want to stick on it.

Module table
--- id, fitting id, module id, module quantity, possibly an ammo id if you want to be able to associate ammo at that level, possibly a module type if you want an easy 'high/medium/low/subsystem/ammo/drone' differentiation.

So you'd have one entry in the fitting table, and multiple entries in the module table.

The module type would be because it's a bit of a pain having to join on dgmTypeAttributes every time you want to pull a list of what module goes in what slot. It breaks with full normalisation, but it's not a biggy, as the module slots don't change

This page is completely wrong anyway, the format does not work like this at all. I don't reccomend storing DNA in the database either, because the format is incomplete, ambiguous and sparsely defined at best.

There is no silver bullet to this problem. Either you have to go with lots of tables and foreign key constraints to do it "properly", or you could store something else in the table (storing the CLF form comes to mind, although you lose the ability to write smart queries to pull specific data out of it).

Well here's an example of how bad it is.

This is not how it works. If you follow this rule, the game will not parse your DNA correctly. According to this rule, here would be a valid proteus DNA:



This doesn't work. You should use this instead:

This line isn't exactly right either, for example if you wanted a fit with only rigs, this rule tells you to use "typeid:::::rigid;qty:" but this is not how the game generates it (also misses the "::" terminator generated on all fits, even those with rigs and charges).

And this doesn't even cover the ambiguity caused by the format itself, such as how to find out where the charges are supposed to go.