Forum Overview :: Deleted Posts :: I think I can help you out, there.

[quote name="jeep"]It just so happens that I have 10 workstations at my office with beardy guru linux on them, and they each have either postgresql, mysql, or oracle installed. It is not trivial to manipulate that much data, but I'm guessing from a technology standpoint I'm in a better spot to fix this than most. I am by no means a programming guru, but I know my way around perl and python, c and java, and more importantly: I know how to extract and manipulate whole databases full of data, since we're constantly moving all or part of our 50 years' worth of records from one server to the next. [quote name="Ice Cream Jonsey"]The database is in Postgresql. The database option supported for this host and for 99% of all webhosts is MySQL. If you would like this thread to become entertaining ask why SB picked Postgresql over MySQL and the processor wars can start hotting up.[/quote] Postgresql is more secure and performs better under load (like say if you decided to change the front page color to edgy black and an avalanche of former voodooextreme readers showed up). Postgresql is also compliant with a lot more standards than mysql, which is usually considered a child's toy by serious developers, and PGSQL is the database shipped with Red Hat Enterprise Linux (under the pseudonym Red Hat Database). However, mysql is great for websites that spend their time pushing text around. SB chose postgresql because he liked BSD and postgres was developed by the same people way back before he was born. Also: he was very...security-conscious, and gawd knows we wouldn't want the government to find out his secret plans to get married, move to Boston and play Star Wars Galaxies. [quote name="Ice Cream Jonsey"]There does not exist -- as far as I've found -- a software tool that will take a Postgresql database and export it into MySQL format. I've been looking for a couple months and not uncovered anything. So a tool needs to be created that will accomplish that. [/quote] Not really. This is going to sound really cheap - and it is - but so far the easiest way to move the non-critical data we store has been phpmyadmin and pgsqladmin. Since I'm a lazy fuck, I install these two things on the workstation I'm sitting at, use one to export everything to whatever approximates ANSI SQL, then use the other to import it, watch the website explode, then tweak the exported sql by hand until it works. It's a little tedious, but me and the techs are pretty good with replacement regexps since we do this all the time. As the nominal sysadmin, I also have the ability to make it convenient for #1 Cable Soul Brother to transmit the data from/to wherever. So I'm at <a href="mailto:jpowers_AT_bostonnine.com">this location</a> and I figure I'm going to need a copy of the old database, a copy of the new one, a copy of the web code, and about a week, maybe two if crisis interferes, at the end of which I can hand you the old database data in a seamlessly importable format. It would be great to do something that isn't "for the betterment of mankind" or whatever my job is. Or you can just take care of it. Seriously, one fast linux desktop with both rdbms, apache and the two phpadmin tools and you're already halfway done...or I'm already halfway done, since I'm sitting at one now. /jeep/ ...and no, I won't GPL the forum code chet stole from "Building Websites With PHP and MySQL." The respective secret shame of everyone who has ever developed for this code is safe with me.[/quote]