Deprecated - Database compatibility

I am attempting to use Drupal on a cluster where the mysql services runs on a non standard port. How do I tell drupal which port to use? I have tried a number of iterations with the $db_url variable but none have worked out so far... For instance the following does not work...

$db_url = "mysql://user:password@mymachine.mylocation.edu:port/DrupalSite";

Thanks

And how to Avoid them.
A Tutorial from IBM's Developer works.
Discover five common database problems that occur in PHP applications -- including database schema design, database access, and the business logic code that uses the database -- as well as their solutions.

If only there were one way to use databases correctly ...

So I'm writing my first module, and I have my installation SQL written up in a separate file. I've seen some other modules do this (events) but then there's another copy of the SQL in the theme.install file. I was wondering if there was a Drupal way to read in the SQL from a file and pass it to db_query, or is it standard to only have a copy of the SQL in the theme.install file? It'd be nice to just have a clean copy of the SQL that isn't butchered together with PHP concats.

Hi.

This file have written myself.

Extract files to drupal root path.

Chance chmod (777) settings to "sites/default/settings.php" and run install.php

If installing it finish, can you delete install.php and reset chmod (755) to settings.php file.

Rar file: http://www.drupal.gen.tr/Drupal_installer_V4.7.rar

((File for Drupal V4.7))

-----------------------------
coming soon Drupal.Gen.TR :)

My node_revisions table contains an entry at (0,0,0) that is full of bizarre characters - is this supposed to be there?

Thanks,
Alex
----------
Contract Web Development

I am running Drupal 4.7.2 with some Chinese content (UTF-8 encoded). It's running fine currently with MySQL 5. Since I have to migrate my web portal to a new host a few days later (they only have MySQL 4.1. I didn't realize it when I ordered the hosting plan), I setup a similar site on my new host with the sql dump from MySQL 5. I know there will be problem downgrading from MySQL 5 to MySQL 4.1 because of the UTF issue. So I backup my database from my current host (MySQL 5) and dumped the SQL file into my localhost MySQL 5. Everything was fine.