major odbc overhaul

Hi everyone, I've done a major overhaul on odbc but am reluctant to cvs it without someone testing it on another platform and db. What I did was to make it possible to compile using unique c and php function names so that more than one of these may be compiled into php, or loaded as .so. So no actual code has changed. I've tested this against odbc on windows, and it seems to function very well. The main reason for doing this is that I want to eventualy be able to add solid, and possibly other db's (if available) in this module on windows. However, it would have caused problems to have more than one of these loaded at any time (in 3.1). So it is necessary to backstep to using solid_*, odbc_*, etc. function names. I'll add a compatibility script (an include file) for backwards compatibility later. Right now, unless ODBC_UNIQUE_NAMES is defined, it should compile exactly as it has in the past, having no effect for 3.0. So who out there will take an email with this stuff attached and test it against other db's? Shane -- PHP Development Mailing List http://www.php.net/ To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net For help: php-dev-help@lists.php.net