On Thu, April 20, 2006 3:48 am, Alain Roger wrote: > personally i do not use MyODBC. i just wrote that this is a common > answer > for such error message. > but why should i check within MySQL documentation if the flag to write > (if > it is really the solution???) belongs to PHP command "mysql_connect" ? Because the flag would have been made up and documented by the MySQL guys. Almost for sure. A handful of exceptions like CURLOPT_BINARYTRANSFER do exist. PHP mysql *MIGHT* have caught that constant as one you need and imported it. Or not. > or is > "mysql_connect" command just a wripping command to ODBC command (and > in this case i understand why to check in MySQL doc.). mysql_connect() in PHP is a thinly-disguised wrapper for a MySQL function of a very similar (if not the same) name. 99% of what many people think of as "PHP" is really a thinly-disguised wrapper for functionality provided by the extension modules. 'Course, it took a TON of work to get those wrappers to work right, to play well together, to not mess up other wrappers in PHP, and so on! But the sooner you understand how PHP really "works" in relation to the extension modules, the better off you'll be. -- Like Music? http://l-i-e.com/artists.htm -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
