Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Steve Ronuken
Fuzzwork Enterprises
1545
|
Posted - 2013.06.20 14:47:00 -
[1] - Quote
Based off: http://cdn1.eveonline.com/data/Odyssey_1.0.7_89602_db.zip
Mysql complete: http://www.fuzzwork.co.uk/dump/mysql55-odyssey-1.07-89602.tbz2
Postgres Complete: http://www.fuzzwork.co.uk/dump/odyssey-1.0.7-89602/postgres-odyssey-1.0.7-89602.sql.bz2
sqlite complete: http://www.fuzzwork.co.uk/dump/odyssey-1.0.7-89602/odyssey107.sqlite.bz2
Individual tables, mysql, XLS/CSV http://www.fuzzwork.co.uk/dump/odyssey-1.0.7-89602/
The trnTranslations table looks good when I try it. If the individual file doesn't work, try the full one. Steve Ronuken for CSM 9!-á I'm starting early :) Handy tools and an SDE conversion Twitter: @fuzzysteve on Twitter |
Amizo Hamma
NoChumps Corp
3
|
Posted - 2013.06.21 00:13:00 -
[2] - Quote
Bravo. I enjoy seeing community contributions like this.
I do have a question, however. How do you do the postgres dump? I assume you do some sort of mssql connector that can import to postgres? Then dump that db. I've played with it before, but I never got it working correctly.
Thanks! |
Steve Ronuken
Fuzzwork Enterprises
1556
|
Posted - 2013.06.21 00:56:00 -
[3] - Quote
I've got an old copy of the Mysql Migration Toolkit, which I use to dump to a pair of files, one with the creation sql, one with the insertion. After a little judicious editing of tinyints, I create the tables, then split up the insertion SQL (as it was too big for my mysql client input buffers)
Then I export it with mysqldump in postgres compatible mode, run it through a postgres converter to make it actually compatible (it's a python one I found a while ago) and import into postgres. Finally, I re-export it, and zip it :)
A little involved, but I'm doing the mysql one for myself anyway, so it's only 3 more steps, which are easily scripted. Steve Ronuken for CSM 9!-á I'm starting early :) Handy tools and an SDE conversion Twitter: @fuzzysteve on Twitter |
Steve Ronuken
Fuzzwork Enterprises
1567
|
Posted - 2013.06.23 03:34:00 -
[4] - Quote
Just to note, the toolkit page now says 1.0.9
It's the same file. They've just renamed it. Steve Ronuken for CSM 9!-á I'm starting early :) Handy tools and an SDE conversion Twitter: @fuzzysteve on Twitter |
Rob Crowley
State War Academy
86
|
Posted - 2013.06.23 08:10:00 -
[5] - Quote
Steve Ronuken wrote:Just to note, the toolkit page now says 1.0.9
It's the same file. They've just renamed it. Nope, they fixed the iconIDs.yaml file. |
Steve Ronuken
Fuzzwork Enterprises
1569
|
Posted - 2013.06.23 16:47:00 -
[6] - Quote
Rob Crowley wrote:Steve Ronuken wrote:Just to note, the toolkit page now says 1.0.9
It's the same file. They've just renamed it. Nope, they fixed the iconIDs.yaml file.
ahh. Same database though.
So I'm not going to do another conversion. Steve Ronuken for CSM 9!-á I'm starting early :) Handy tools and an SDE conversion Twitter: @fuzzysteve on Twitter |
Nari Neya
Vhero' Multipurpose Corp
1
|
Posted - 2013.06.25 02:01:00 -
[7] - Quote
Steve Ronuken wrote:Rob Crowley wrote:Steve Ronuken wrote:Just to note, the toolkit page now says 1.0.9
It's the same file. They've just renamed it. Nope, they fixed the iconIDs.yaml file. So I'm not going to do another conversion.
Same issue as with previous dump (I wrongly attributed it to Jercy first time). The dump is double-encoded, all rows in trnTranslations are mangled. |
Steve Ronuken
Fuzzwork Enterprises
1580
|
Posted - 2013.06.25 09:30:00 -
[8] - Quote
Nari Neya wrote:Steve Ronuken wrote:Rob Crowley wrote:Steve Ronuken wrote:Just to note, the toolkit page now says 1.0.9
It's the same file. They've just renamed it. Nope, they fixed the iconIDs.yaml file. So I'm not going to do another conversion. Same issue as with previous dump (I wrongly attributed it to Jercy first time). The dump is double-encoded, all rows in trnTranslations are mangled.
I just tried restoring the trnTranslations table, just using: bzcat trnTranslations.sql.bz2|mysql databasename
It, while I don't read japanese, appears to be showing up correctly? Steve Ronuken for CSM 9!-á I'm starting early :) Handy tools and an SDE conversion Twitter: @fuzzysteve on Twitter |
Nari Neya
Vhero' Multipurpose Corp
1
|
Posted - 2013.06.25 12:14:00 -
[9] - Quote
I don't read Japaneze either, but I can open the dump file in hex viewer and clearly see, that the bytes in multibyte Cyrillic strings are not formed with 0xD0 prefix, but with 0xC3 0x90, consistently repeating after each two other octets, which clearly indicating that the string is double-encoded into UTF-8. Also, I didn't mean separate tables export. But the mysql55-odyssey-1.07-89602.tbz2 (full package). |
Steve Ronuken
Fuzzwork Enterprises
1580
|
Posted - 2013.06.25 12:34:00 -
[10] - Quote
Weird. I'm not doing anything unusual in the export. mysqldump should be exporting files, by default, as utf8. And I'm not passing any directives to change that.
Hmm. It's probably the shell causing trouble. On the next time round, I'll try avoiding using any shell redirections. Steve Ronuken for CSM 9!-á I'm starting early :) Handy tools and an SDE conversion Twitter: @fuzzysteve on Twitter |
|
Steve Ronuken
Fuzzwork Enterprises
1580
|
Posted - 2013.06.25 13:50:00 -
[11] - Quote
Steve Ronuken wrote:Weird. I'm not doing anything unusual in the export. mysqldump should be exporting files, by default, as utf8. And I'm not passing any directives to change that.
Hmm. It's probably the shell causing trouble. On the next time round, I'll try avoiding using any shell redirections.
http://www.fuzzwork.co.uk/dump/mysql55-odyssey-1.09-89602.tbz2
/Should/ have single encoding. Steve Ronuken for CSM 9!-á I'm starting early :) Handy tools and an SDE conversion Twitter: @fuzzysteve on Twitter |
Nari Neya
Vhero' Multipurpose Corp
1
|
Posted - 2013.06.25 19:05:00 -
[12] - Quote
Curiouser and curiouser. Files are slightly different, but the difference is in range of a few bytes. And the double encoding issues are still there. Mind if I ask, how do you construct the file? |
Nari Neya
Vhero' Multipurpose Corp
1
|
Posted - 2013.06.25 19:29:00 -
[13] - Quote
P.S. I doubt it is redirect. More like wrong database locale settings cause additional conversion. |
Steve Ronuken
Fuzzwork Enterprises
1584
|
Posted - 2013.06.25 22:39:00 -
[14] - Quote
The export is done with:
mysqldump -u root -p --default-character-set=utf8 --databases sdeodyssey107 -r mysql55-odyssey-1.09-89602.sql
The database is set with a utf8 default character set, and so are the individual tables. Steve Ronuken for CSM 9!-á I'm starting early :) Handy tools and an SDE conversion Twitter: @fuzzysteve on Twitter |
Nari Neya
Vhero' Multipurpose Corp
1
|
Posted - 2013.06.26 07:23:00 -
[15] - Quote
Export is fine. But how do you import it? |
Steve Ronuken
Fuzzwork Enterprises
1587
|
Posted - 2013.06.26 09:24:00 -
[16] - Quote
Nari Neya wrote:Export is fine. But how do you import it?
Well, to reimport that export, I'm just using
mysql databasename < filename.sql
If you're talking about the whole process, look up a few posts. Steve Ronuken for CSM 9!-á I'm starting early :) Handy tools and an SDE conversion Twitter: @fuzzysteve on Twitter |
Nari Neya
Vhero' Multipurpose Corp
1
|
Posted - 2013.06.26 09:47:00 -
[17] - Quote
Ok, let me rephrase it. Does the database before export contains properly encoded strings? |
Golden Gnu
EVE University Ivy League
95
|
Posted - 2013.06.26 10:23:00 -
[18] - Quote
You should update your post (or create a new one). Odyssey 1.0.9 is out and you already converted it. ******* awesome as always - best source for data in the known universe! o7 Download is the meaning of life, upload is the meaning of intelligent life http://eve.nikr.net - home of jEveAssets |
Steve Ronuken
Fuzzwork Enterprises
1587
|
Posted - 2013.06.26 10:44:00 -
[19] - Quote
Golden Gnu wrote:You should update your post (or create a new one). Odyssey 1.0.9 is out and you already converted it. ******* awesome as always - best source for data in the known universe! o7 EDIT:It was giving me some trouble, because the tar file did not have an file extension
1.0.9 is the same database as 1.0.7.
The only change was some of the yaml files. Steve Ronuken for CSM 9!-á I'm starting early :) Handy tools and an SDE conversion Twitter: @fuzzysteve on Twitter |
Nari Neya
Vhero' Multipurpose Corp
1
|
Posted - 2013.06.26 21:01:00 -
[20] - Quote
Golden Gnu wrote:You should update your post (or create a new one). Odyssey 1.0.9 is out and you already converted it. ******* awesome as always - best source for data in the known universe! o7 EDIT:It was giving me some trouble, because the tar file did not have an file extension 1.0.9 was GZIP'd, rather than BZIP'd. Rename it to ".tgz" or run tar -xzf instead of -xjf |
|
Acid Kanshi
Deep Core Mining Inc. Caldari State
38
|
Posted - 2013.06.27 08:29:00 -
[21] - Quote
Sweet thanks! EVE-Cost is a manufacturing tool for EVE players. http://www.eve-cost.eu |
Jess Technite
Almost Absolute
0
|
Posted - 2013.06.28 13:10:00 -
[22] - Quote
Don't know what have done. I have imported your PostgreSQL script and now the VB.NET throws this message in the first query:
"ERROR [42883] ERROR: operator does not exist: integer = boolean;"
The curious fact is that googling have seen that it's a message that gives in psql 8.3 and superior, and have never changed this PSQL version (9.1). In addition, the method to solve it (setInt or whatever to force the type for every field) doesn't work in the sql string for VB.NET. |
Steve Ronuken
Fuzzwork Enterprises
1591
|
Posted - 2013.06.28 13:21:00 -
[23] - Quote
Huh.
What's the query? Steve Ronuken for CSM 9!-á I'm starting early :) Handy tools and an SDE conversion Twitter: @fuzzysteve on Twitter |
Jess Technite
Almost Absolute
0
|
Posted - 2013.06.28 13:28:00 -
[24] - Quote
sql = "SELECT ""invTypes"".""typeID"", ""typeName"", ""groupID"" FROM ""invTypes"", ""invBlueprintTypes"" WHERE ""invTypes"".""typeID"" = ""productTypeID"" and ""published"" = TRUE"
In VB.NET with tables / fields with double quoted you must put this way. Otherwise it says doesn't find that field. |
Steve Ronuken
Fuzzwork Enterprises
1591
|
Posted - 2013.06.28 15:06:00 -
[25] - Quote
Jess Technite wrote:sql = "SELECT ""invTypes"".""typeID"", ""typeName"", ""groupID"" FROM ""invTypes"", ""invBlueprintTypes"" WHERE ""invTypes"".""typeID"" = ""productTypeID"" and ""published"" = TRUE"
In VB.NET with tables / fields with double quoted you must put this way. Otherwise it says doesn't find that field.
Try adjusting it to published=1
published will just be an integer.
Alternatively, change the database column type to boolean (http://stackoverflow.com/questions/1740303/postgres-alter-column-integer-to-boolean may be useful in this case) Steve Ronuken for CSM 9!-á I'm starting early :) Handy tools and an SDE conversion Twitter: @fuzzysteve on Twitter |
Jess Technite
Almost Absolute
0
|
Posted - 2013.06.28 17:15:00 -
[26] - Quote
Steve Ronuken wrote:Jess Technite wrote:sql = "SELECT ""invTypes"".""typeID"", ""typeName"", ""groupID"" FROM ""invTypes"", ""invBlueprintTypes"" WHERE ""invTypes"".""typeID"" = ""productTypeID"" and ""published"" = TRUE"
In VB.NET with tables / fields with double quoted you must put this way. Otherwise it says doesn't find that field. Try adjusting it to published=1 published will just be an integer. Alternatively, change the database column type to boolean (http://stackoverflow.com/questions/1740303/postgres-alter-column-integer-to-boolean may be useful in this case)
True. They changed from boolean to integer and forgot it. It works :) |
Zanto Snix
Formosa Research Center Apocalypse Now.
0
|
Posted - 2013.07.03 06:21:00 -
[27] - Quote
there is a new version Odyssey_1.0.12_89967_db.zip, any different from the db files or just yaml changed? |
Steve Ronuken
Fuzzwork Enterprises
1604
|
Posted - 2013.07.03 10:55:00 -
[28] - Quote
Zanto Snix wrote:there is a new version Odyssey_1.0.12_89967_db.zip, any different from the db files or just yaml changed?
Missed that release.
I'll go have a dig into it. probably has some minor DB updates (for the sleeves and so on.) Steve Ronuken for CSM 9!-á I'm starting early :) Handy tools and an SDE conversion Twitter: @fuzzysteve on Twitter |
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |