| Issue 1: | Models and importers for staStationTypes + staOperations |
1 of 10
Next ›
|
| 1 person starred this issue and may be notified of changes. | Back to list |
Here is my patch that allows eve_db to import these tables. I mostly followed off the previous examples already written into the project. I used http://wiki.eve-id.net/Database_Tables_-_Stations to determine which ForeignKeys point where, and it seems that these two tables are dependencies of each other? This patch will successfully import the data from the latest dump after the eve_import_ccp_dump being run for each importer, twice. I am fairly confident that improvements could be made to my code, but I am at a loss as to what to do next. I am going to continue on with the mapDenormalize and staStations models and importers. Would love comments or ideas, thanks. Also, is uploading my changed files fine, or would diffs be preferred?
Mar 8, 2010
Project Member
#1
Ryan.Bis...@gmail.com
Mar 8, 2010
Problem appears to be with my model and/or importer....attempting to show fields any of the racial type fields, ie. 'caldari_station_type', 'minmatar_station_type', results in the error message "Caught an exception while rendering: 'EVEStationType' object has no attribute 'name'" Will update with fix or additional information.
Mar 8, 2010
If you don't mind, go to the root directory of django-eve-db and do the following, assuming you're on Linux/Unix: svn diff > patchfile.diff This will perform an SVN diff on your checkout, comparing your local copy to the remote repository. If you're running on Windows, you'll probably want to right click in the directory and look for a way to create a patch or show modifications.
Mar 8, 2010
Here's the diff.
Mar 9, 2010
(No comment was entered for this change.)
Status:
Started
Labels: -Type-Defect Type-Enhancement
Mar 9, 2010
Cool, got this merged into trunk with the following changes: * Your error was due to returning self.name, where self.name didn't exist in that station model. * Renamed item_name on mapDenormalize to just 'name'. This is not something you could have known beforehand, just me trying to simplify things a little bit, and to preserve consistency. * The staStationType table is kind of tricky. The stationTypeID field points to an invType object, it's not the primary key (id) for the table, though. I've added a 'type' field and changed the importer so you can see what I mean. * Added the 'type' -> EVEInventoryType field to EVEStationType. * Changed related_names on EVEStationOperation *_station_type fields. For there not being any documentation on this stuff yet, excellent job. We'll see another patch or two from you (if you have further things to add), and see about opening up commit access if you continue your involvement. Great work!
Mar 9, 2010
(No comment was entered for this change.)
Status:
Fixed
|