mysql help

hi all.
i was playing around with mysql when i found
trouble to insert a record that had a "'" caracter in the middle like: Ocean's Eleven.
How can insert this caracter "'" in the record?
Another thing, why took a script long time to display 200 records to a webpage and still the page made a lot of refresh's until stop, and doing the same thing using a odbc connection took only half a second to show the same results?
thanks.

as far as the quotes, you'll need to add slashes (escape characters) to the data before inserting, and remove the slashes when retrieving the data. in php, you'd use addslashes() and stripslashes()

no clue about your other question.

what database where you using in the odbc instance? It seems very unlikely you were getting better performance in terms of speed with any database or scripting language than apache/php/mysql. Apparently the new embedded (in php) SQLite is faster than MySQL but I haven't worked with it yet. If your machine was thrashing it might have been a piece of bad code, if it was a web based appliaction it was probably one of those instances where the vagaries of the net slow down your connection.

hi...thanks for the reply's.
about the second question iwas using an odbc conection on a MS Acess database.
The script dumped the records very fast and without refreshing,then i made a script to dump the records from Acess to a MySql database, and using the same structural code i was unable to get the same speed

I am uncertain how you were able to run the code on an access database and then on a MySQL db as one is primarily unix/linux based and the other is windows. PHP does not run as well on a NT/Windows server as it does on linux/unix/freeBSD because it can't run inline as part of the webserver (apache) and is an external call. Access is certainly not faster than MySQL, especially as part of a web app, perhaps part of the issue was different servers or the configuration of the servers.

php runs just fine on apache on win nt (2k, xp).

as for that "inline" remark, you are probably thinking about running php as apache module (as oposed to cgi), well, php also runs just fine as apache module...

actually I meant just the reverse as far as cgi and an apache module. The apache module is the fastest way to implement PHP by far. No commercial hosts offer NT servers with Apache because it doesn't make sense in terms of cost. If you're going to have the added cost of NT servers then you'll undoubtedly be planning on supporting ASP - MSSQL - Access - .NET etc. because many people want that environment. People who are offering Apache/PHP/MySQL are almost invariably running on Linux/Unix/FreeBSD because it doesn't make sense to do it cross platform for a higher cost with no added functionality. I run Foxserv locally as a dev environment (on 2k) but what I really meant was that people running MS servers run IIS or .NET and not Apache so PHP has to be a remote call which takes longer to process than the inline module does. Kind of like chilisoft ASP in reverse.