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.
 

Retribution 1.0 SDE Issues (CCPPrismX twitt version)

First post
Author
Previous Topic Next Topic
Lluerssen
PHUB Corporation
#21 - 2012-12-07 11:59:23 UTC  |  Edited by: Lluerssen
http://cl.ly/1308150r0p1E
Removed invTypes, omg -.-

> SELECT count(*) FROM `invTypes` WHERE typeName LIKE '%blueprint%';
3053 vs 112

Sister of EvE: http://SisterOfEvE.ru/ Loot History Analyzer: http://SisterOfEvE.ru/loot_history/
CCP Prism X
C C P
C C P Alliance
#22 - 2012-12-07 12:01:44 UTC
Yeah I accidentally put an inner join on the description, change log clearly states that was a mistake. Gimmie a few moments.

CCP Prism X

Programmer on Team Gridlock & Expert Ranter
Vessper
Dark Mason Society
#23 - 2012-12-07 12:07:18 UTC
mapSolarSystems has no rows in the new SDE?
CCP Prism X
C C P
C C P Alliance
#24 - 2012-12-07 12:10:14 UTC
Vessper wrote:
mapSolarSystems has no rows in the new SDE?


Dunno about the broken one I generated but the one I'm uploading now seems cool:

SELECT COUNT(*) FROM mapSolarSystems

7929

(1 row(s) affected)

CCP Prism X

Programmer on Team Gridlock & Expert Ranter
Vessper
Dark Mason Society
#25 - 2012-12-07 12:12:50 UTC
Yes, it was the one released an hour or so ago.
CCP Prism X
C C P
C C P Alliance
#26 - 2012-12-07 12:19:31 UTC
Yeah that makes sense. The sun types do not have a description authored. Therefore they did not get dumped into the types table, and thus all solar systems were removed as they have a sunTypeID authored and all sun types were deleted.

However:
New fixedfixed version uploaded to same addy and CDN cache purged.
That's attempt two, I'm aiming for "Third time's the charm!" though! Lol

CCP Prism X

Programmer on Team Gridlock & Expert Ranter
Vessper
Dark Mason Society
#27 - 2012-12-07 12:51:58 UTC
The eveUnits table is missing unitIDs 103, 122 and 129, and 122 is used by many of the attributes (103 and 129 appear unused). The only thing I can see that these have in common is that the unit display name is null (or was at least in the Inferno SDE).

It's easy to add that one line in manually but just thought I'd raise the issue anyway.
Vessper
Dark Mason Society
#28 - 2012-12-07 13:19:24 UTC
The dgmAttributeTypes table is missing attributes for the low, mid, hi and rig slots of a ship (IDs 12,13,14,1137) and the dgmTypeAttributes table is missing all entries containing these IDs.

Not sure if it's related to the above bearing in mind unitID 122 is "Fitting Slots".
CCP Prism X
C C P
C C P Alliance
#29 - 2012-12-07 13:21:12 UTC
Probably is.

And this is why we should be releasing the SDE before deploying the expansion. I'm going to wait for some more issues to crop up before generating another one.

CCP Prism X

Programmer on Team Gridlock & Expert Ranter
Sidrat Flush
School of Applied Knowledge
#30 - 2012-12-07 13:23:01 UTC
When the tables are converted to yaml will errors be easier or harder to spot?

Its time to stand up against the bad empire based CEO telling falsehoods about what new characters can accomplish and pushing them towards an in game experience of drudgery and loneliness keeping them in the shadow of ignorance for at nest their own profit at worse apathy towards all the experiences that Eve has to offer.
Dei
Cosmic Core Industries
#31 - 2012-12-07 20:13:53 UTC
Just out of interest. How much does data structure and data change in the days before a release?
Dread Nanana
Doomheim
#32 - 2012-12-08 16:38:43 UTC
Sidrat Flush wrote:
When the tables are converted to yaml will errors be easier or harder to spot?


Yes, YAML - a structure known for its strong consistency checks and resilience to mistakes Ugh

The straight MSSQL dump is much superior, at least if it had any constraints maybe. Without foreign key constraints, we get what we get.
Dei
Cosmic Core Industries
#33 - 2012-12-08 16:59:02 UTC
Not sure why there aren't any integrity scripts. It sounds like this is a fairly manual process to get us the metadata. Is the actual datastructure that horrible to work with?
Sidrat Flush
School of Applied Knowledge
#34 - 2012-12-08 17:12:15 UTC
Dei wrote:
Not sure why there aren't any integrity scripts. It sounds like this is a fairly manual process to get us the metadata. Is the actual datastructure that horrible to work with?


There's data they don't want us to have only thong comes to mind is the NPC rat information although it used to be included.

I'm sure there's other stuff just because would be interesting to get more information though.

So YAML and I haven't used it will be worse to work with, is a yaml sheet easy to convert to an access table or better yet a straight to excel pivot table?

Its time to stand up against the bad empire based CEO telling falsehoods about what new characters can accomplish and pushing them towards an in game experience of drudgery and loneliness keeping them in the shadow of ignorance for at nest their own profit at worse apathy towards all the experiences that Eve has to offer.
Desmont McCallock
#35 - 2012-12-10 16:51:32 UTC
IDs 363369, 363370, 363371 are missing from invMarketGroups related to IDs 350916, 363355, 363356, 363357, 363358, 363359 in invTypes. All those are DUST 514 related data though.
Zifrian
The Frog Pond
Ribbit.
#36 - 2012-12-11 20:52:29 UTC
So a week later and still no fixed data?

Maximze your Industry Potential! - Download EVE Isk per Hour!

Import CCP's SDE - EVE SDE Database Builder
Desmont McCallock
#37 - 2012-12-13 18:12:56 UTC
No news, is bad news. (Also bumping thread)
Dei
Cosmic Core Industries
#38 - 2012-12-13 20:32:39 UTC
PrismX this morning said he was waiting on more reports on what was wrong. :S
Desmont McCallock
#39 - 2012-12-14 05:42:36 UTC
He already stated that in his last post. On one hand he's justified. On the other hand I'm about to explode by the criticism I receive why I haven't updated EVEMon yet. I'm between a rock and a hard place.
darius mclever
#40 - 2012-12-14 12:15:47 UTC
+1 on releasing a dump now

and then maybe using the waiting time for writing a script that validates that the dump is consistent.