Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Desmont McCallock
175
|
Posted - 2012.05.22 19:39:00 -
[1] - Quote
http://community.eveonline.com/community/toolkit.asp |
Kronus Heilgar
Caldari Provisions Caldari State
6
|
Posted - 2012.05.22 21:45:00 -
[2] - Quote
MySQL port? Anyone? Anyone? This is not the signature you're looking for. |
Steve Ronuken
Fuzzwork Enterprises
417
|
Posted - 2012.05.22 22:27:00 -
[3] - Quote
Kronus Heilgar wrote:MySQL port? Anyone? Anyone?
couple of hours and I'll have one ready. (hopefully) FuzzWork Enterprises http://www.fuzzwork.co.uk/ Blueprint calculator, invention chance calculator, isk/m3 Ore chart-á and other 'useful' utilities. |
Steve Ronuken
Fuzzwork Enterprises
417
|
Posted - 2012.05.23 10:26:00 -
[4] - Quote
I've heard that some people are getting really poor import performance with the export above. so I've also taken the one below, which might run faster for you. It's using the extended insert option, which can improve performance (With some side effects on compatibility and resumability. Probably won't affect you.)
http://www.fuzzwork.co.uk/dump/inferno10/mysql55-inferno10-extended.sql.bz2 FuzzWork Enterprises http://www.fuzzwork.co.uk/ Blueprint calculator, invention chance calculator, isk/m3 Ore chart-á and other 'useful' utilities. |
Steve Ronuken
Fuzzwork Enterprises
417
|
Posted - 2012.05.23 11:02:00 -
[5] - Quote
Blerg. apparently some folks are having trouble downloading from my site. So, two alternates:
http://dl.eve-files.com/media/1205/mysql55-inferno10-extended.7z https://www.dropbox.com/s/lmvbu40k1ftb5jt/mysql55-inferno10-extended.sql.bz2 FuzzWork Enterprises http://www.fuzzwork.co.uk/ Blueprint calculator, invention chance calculator, isk/m3 Ore chart-á and other 'useful' utilities. |
Khorkrak
War Tribe
2
|
Posted - 2012.05.23 18:10:00 -
[6] - Quote
Thanks Steve - I'll be applying this tonight and appreciate the faster queries. This form would be even faster though for MySQL.
load data local infile 'factions.dat' into table factions fields terminated by '\t' lines terminated by '\n';
I use that for my project's trimmed down SDE tables for MySQL along with the corresponding equivalent for PostgreSQL. It's a tad annoying though that there's no way to do it inline in one file with MySQL though but that's par for the course.
COPY factions (faction_id, faction_name) FROM stdin; 500001Caldari State 500002Minmatar Republic 500003Amarr Empire 500004Gallente Federation Extraordinary claims require extraordinary evidence |
Khorkrak
War Tribe
2
|
Posted - 2012.05.24 00:29:00 -
[7] - Quote
Just loaded the latest dump and wow - way faster than previously - thanks so much. Extraordinary claims require extraordinary evidence |
diabeteman
ICE is Coming to EVE
11
|
Posted - 2012.05.30 01:47:00 -
[8] - Quote
Hey guys :)
I'm desperate for sqlite & postgresql conversions of the datadump.
I usually get them from here : http://zofu.no-ip.de/ , but the guy who maintains them appears to be on vacation :D
I tried to restore the mssql dump and export it to a SQL file. Then follow the steps described in http://zofu.no-ip.de/esc10/work/DBHOWTO But this doesn't work. The export format I make seems not to be compliant to what the perl scripts want.
Could someone help ?
thx in advance <3
-diab Initiator and CTO of Eve Corp. Management |
Steve Ronuken
Fuzzwork Enterprises
429
|
Posted - 2012.05.30 02:12:00 -
[9] - Quote
I've got the mysql conversion done.
So I've taken what should be a postgres compatible export from mysql. (just mysqldump with the --compatible=postgresql option)
http://www.fuzzwork.co.uk/dump/inferno10/pgsql/pgsqlcompat-inferno1.0.sql.bz2
with the following, it may work for you. Specifically the Convert and Import section. http://en.wikibooks.org/wiki/Converting_MySQL_to_PostgreSQL FuzzWork Enterprises http://www.fuzzwork.co.uk/ Blueprint calculator, invention chance calculator, isk/m3 Ore chart-á and other 'useful' utilities. |
diabeteman
ICE is Coming to EVE
11
|
Posted - 2012.05.30 08:31:00 -
[10] - Quote
Thanks mate :)
I'll try to convert it tonight and if i'm successful I'll make it available on the net. Initiator and CTO of Eve Corp. Management |
|
Tonto Auri
Vhero' Multipurpose Corp
24
|
Posted - 2012.05.30 08:39:00 -
[11] - Quote
Khorkrak wrote:Thanks Steve - I'll be applying this tonight and appreciate the faster queries. This form would be even faster though for MySQL.
load data local infile 'factions.dat' into table factions fields terminated by '\t' lines terminated by '\n'; LOAD DATA LOCAL is even further from compatibility with various environments, than extended inserts. If you want performance evaluation for different insertion methods, you may dig up old SDD threads on archived forum. |
Tonto Auri
Vhero' Multipurpose Corp
24
|
Posted - 2012.05.30 08:54:00 -
[12] - Quote
Dug it up for you. http://community.eveonline.com/ingameboard.asp?a=topic&threadID=1376938&page=1#16 |
diabeteman
ICE is Coming to EVE
11
|
Posted - 2012.05.30 12:20:00 -
[13] - Quote
YAY! It worked!
On the wiki page you linked, I found a ruby utility that does the translation between mysql and postgres :)
Here are the conversions I made: http://releases.eve-corp-management.org/eve_sde/ You will find the scripts I used to do this (instructions are in the 'config' file).
I hope others will have some use of this Initiator and CTO of Eve Corp. Management |
Desmont McCallock
179
|
Posted - 2012.05.30 12:36:00 -
[14] - Quote
Doesn't this suffice? http://zofu.no-ip.de/esc10/esc10-pgsql-v1.sql.bz2 |
diabeteman
ICE is Coming to EVE
11
|
Posted - 2012.05.30 12:37:00 -
[15] - Quote
this is not inferno. Read my first post ^^ Initiator and CTO of Eve Corp. Management |
Desmont McCallock
179
|
Posted - 2012.05.30 12:39:00 -
[16] - Quote
My bad. |
diabeteman
ICE is Coming to EVE
11
|
Posted - 2012.05.31 23:14:00 -
[17] - Quote
The conversions I did had encoding problems, I created new clean ones
http://releases.eve-corp-management.org/eve_sde/inferno10/inferno10-psql-2.sql.bz2 http://releases.eve-corp-management.org/eve_sde/inferno10/inferno10-sqlite-2.db.bz2
Please tell me if there is anything wrong :) Initiator and CTO of Eve Corp. Management |
Coreth Oake
Bacon Chip Cookie Ice Cream Sammich
0
|
Posted - 2012.06.03 09:53:00 -
[18] - Quote
All the identifiers in the psql conversion are quoted, which makes them case sensitive. This is a problem because to reference case sensitive identifiers you have to use quotes everywhere, for example, SELECT * FROM invTypes doesn't work, you would have to use SELECT * FROM "invTypes" instead. |
Steve Ronuken
Fuzzwork Enterprises
438
|
Posted - 2012.06.03 18:15:00 -
[19] - Quote
The next SDE what comes out, I'll see about a PostGres conversion too. No promises, but it's likely enough to annoy me into doing it.
Anyway, for the sensitivity issue, why don't you just:
ALTER TABLE "invTypes" RENAME TO invtypes;
? There should be an easy way to list all the tables, and if it's a select statement, then you can use that statement to generate all the sql you need to run. FuzzWork Enterprises http://www.fuzzwork.co.uk/ Blueprint calculator, invention chance calculator, isk/m3 Ore chart-á and other 'useful' utilities. |
Coreth Oake
Bacon Chip Cookie Ice Cream Sammich
0
|
Posted - 2012.06.04 14:49:00 -
[20] - Quote
Steve Ronuken wrote: Anyway, for the sensitivity issue, why don't you just:
ALTER TABLE "invTypes" RENAME TO invtypes;
The problem is it affects all the identifiers, including column names too. I am sure it would be possible to write some script to fix it, but at that point I may as well do the conversion from scratch for a similar amount of *effort*. |
|
Steve Ronuken
Fuzzwork Enterprises
438
|
Posted - 2012.06.04 16:00:00 -
[21] - Quote
http://stackoverflow.com/questions/10086532/postgresql-how-can-i-convert-all-columns-in-my-database-to-case-insensitive
\t on select 'ALTER TABLE '||'"'||table_name||'"'||' RENAME COLUMN '||'"'||column_name||'"'||' TO ' || lower(column_name)||';' from information_schema.columns where table_schema = 'public' and lower(column_name) != column_name; \g /tmp/go_to_lower \i /tmp/go_to_lower
\o /tmp/go_to_lower select 'ALTER TABLE '||'"'||tablename||'"'||' RENAME TO ' || lower(tablename)||';' from pg_tables where schemaname = 'public'; psql -U username database < /tmp/go_to_lower FuzzWork Enterprises http://www.fuzzwork.co.uk/ Blueprint calculator, invention chance calculator, isk/m3 Ore chart-á and other 'useful' utilities. |
Coreth Oake
Bacon Chip Cookie Ice Cream Sammich
0
|
Posted - 2012.06.04 17:30:00 -
[22] - Quote
I suppose that will do, thanks. |
Khorkrak
War Tribe
3
|
Posted - 2012.06.04 17:59:00 -
[23] - Quote
I went through much of the same hassle initially. Converting to all lowercase though results in even more ridiculous names such as mapsolarsytems and invuniquenames. I put up with that for a few weeks and then finally had enough of it. I ended up abandoning their ugly naming convention and simply changed everything to lowercase, underscore separated sans the Hungarian notation-esque prefix to convert their schema into something much more tolerable.
invSolarSystems becomes solar_systems invTypes becomes types
and so on. No more case sensitivity issues, less typing / space consumption in code, less clutter, more readable. Win. The only issue is the invNames table becoming names which is a reserved word in SQL-92 and SQL-99 but not in SQL-2003 interestingly. Works fine in MySQL and PostgreSQL.
SQL Reserved Words Extraordinary claims require extraordinary evidence |
diabeteman
ICE is Coming to EVE
11
|
Posted - 2012.06.26 19:38:00 -
[24] - Quote
Coreth Oake wrote:All the identifiers in the psql conversion are quoted, which makes them case sensitive. This is a problem because to reference case sensitive identifiers you have to use quotes everywhere, for example, SELECT * FROM invTypes doesn't work, you would have to use SELECT * FROM "invTypes" instead. Yeah this is more a problem of the pgsql interpreter which IS case sensitive but has a strange behaviour : when you don't put double quotes, the interpreter considers that everything is lowercase (out of the blue...).
It means that invBlueprintTypes will be interpreted as invblueprinttypes
I guess you will have to add double quotes everywhere in your SQL statements (which is a good practice anyway ^^) Initiator and CTO of Eve Corp. Management |
Steve Ronuken
Fuzzwork Enterprises
470
|
Posted - 2012.06.26 19:41:00 -
[25] - Quote
Oracle does much the same thing. but it uppercases everything that's not quoted. FuzzWork Enterprises http://www.fuzzwork.co.uk/ Blueprint calculator, invention chance calculator, isk/m3 Ore chart-á and other 'useful' utilities. |
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |