eve db tables... incomplete?

[Marcaunon]

Hi

I'm new to eve-django
I've recently started looking at this because google docs is
inadequate for what I want todo :)

Anyways I've installed django worked through the tutorials..
got django-eve in place
imported db.. it seemd to have worked.. although only took 7 mins and
not 1hour like promised?
well ccp_dump.db is 303mb and my djangoeve.db (sqlite3) is now 212MB..
so I suppose most info is in?

ok then I did python manage.py shell
and started browsing around trying to make sense of what is going on..
I must say the info is nicely sorted and all that, will be easy to
work with I think.

But the first thing I need for my project is BP information.
tech1 and tech2.. invention and production stuff..
and it seems incompleted..

ok for tech 1 it seems semi ok..
for i in tech1bpo.product_type.material_set.all(): print i
spits out nice tech1 mineral values needed to produce item.

but what I'm missing and can't find is this:
1. invention information.. which and how many datecores?
2. tech2 other than base mineral values.. components required to build
a sleipnir for example?

It seems the whole invTypeMaterial thing is limited to minerals only..
where is the rest of the info hidden?

thank you for your support

[Dylan Liverman]

Hi,

The table you're looking for is ramTypeRequirements which contains most of the fun parts of Industry.  You should be able to make out what is going on from the table itself, but the Eve Dev Wiki has a bunch of SQL examples here: http://wiki.eve-id.net/Bill_of_Materials

Planetary Interaction stuff is a completely different story that I haven't looked at yet.

I've been wanting to add some functions to make things easier, but the power of laziness is strong.

On the topic of the DB size, CCP likes to move tables around sometimes, Incarna may have changed some things.  I believe the docs that cited an hour estimated import time were written before the import code got a HUGE performance boost.

Hope this helps!

Dylan

--
You received this message because you are subscribed to the Google Groups "Django and EVE Online" group.
To post to this group, send email to djang...@googlegroups.com.
To unsubscribe from this group, send email to django-eve+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-eve?hl=en.

[Heinrich du Toit]

thanx for the help!
This is very nice indeed.

Now only need to find the time to hack out my dream program :D

--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

[Béres Botond]

Well 7 mins certainly seems a bit too low, I don't remember making it
that fast :P.

The original import ran for more like several hours not 1 hour, after
the import rewrite I think my test imports took around ~40 min.
So I think it's fairly likely a few big tables have been renamed/
moved, unless you ran it on some high end machine?

Back then I've tested it on a fairly beefy laptop, but HDD speed is
it's weak point, so maybe you *can* get much better import times.

Unfortunately I don't have time to check currently, maybe I can have a
look this weekend.

Botond

[Dylan Liverman]

I ran the importers on my laptop using SQLite3.  It took about 9 minutes with the big one, mapDemormalize taking 2:30.  The Incarna DB isn't out yet, latest is Incursion 1.5.  

mapDenormalize used to take 9 hours on this laptop.  Its about 1 step above a netbook in size/performance.  Based on that, I think the almost instantaneous times on the other tables are well within reason.  The new importers are awesome.

Dylan