[thelist] Moving: NT/2K to *nix, ASP to PHP, SQL to MySQL . . .?

[Sølve Horrigmoe]

databarn wrote:

> Along those lines, what am I going to run into moving the web stuff over from ASP to PHP?  I realize there's going to be a learning curve, but what possibly fatal pitfalls do I need to know to dodge?  I don't think the database conversion issues will be significant (I don't say they won't be vexing!), since I'm fairly comfortable there.  I've a feeling, though, that the web conversion is going to be fraught with experiences that I'd probably rather not have - at least, not all at once.

I've done some porting of asp/ ms sql scripts to php/ mysql for a client. The original code was produced by a third party and was the backend for an e-learning course based on Macromedia Director files using the asp scripts to store and retrieve course information and content from the db.

I used asp2php by Micheal Kohn ( http://asp2php.naken.cc/ ) for a quick fix for the convertion. Luckily, the developers had used generic SQL statements in their code, knowing thet a conversion to a more serious server system could happen in the future.

This is not a preferred solution, but in many cases Kohn's script will do the trick. It might give you a workable set of PHP scripts quickly, then you could rewrite them as you learn over time. The db conversion is done manually. A suggestion for moving data was posted on this list earlier this week, I think..(create identical schemas in mysql, export data as comma-delimited, import in mysql).

If your system is to handle transactions, you might want to consider PostgreSQL, which has ACID properties - mysql doesn't .

-Sølve