ODBC functions for PHP 4, improvements, survey
| From: | Leo Baschy | Date: | Sat, 11 Mar 2000 03:31:53 +0000 |
| Subject: | ODBC functions for PHP 4, improvements, survey | ||
| Groups: | php.version4 | ||
| Request: | Send a blank email to php-version4+get-11905@lists.php.net to get a copy of this message | ||
Greetings,
I have spent about half of my work / coding time in the last two months on coding (changes to the
source code of) the ODBC module of PHP. I had / have specific needs for a project. I am about
ready to roll my code into the official version.
With PHP 4 about to go final I might as well make sure / take some responsibility for / coordinate
that ODBC works well in PHP 4. (Unless someone else tells me they want to do that right now.)
To smooth the process (avoid conflicts) I would like to know (from _you_):
- are you using ODBC ?
- which database
- which operating system
- which Web server
- which version of PHP
- are you changing PHP source yourself ?
- are you actively changing PHP's ODBC functions
- are you compiling yourself or are you using the built binary ?
(would you notice if something breaks?)
- which compiler environment
- whatever else you think matters
If you don't want to reply to the list <php4beta@lists.php.net> you can reply to me at
<nirvana@got.net>.
My answers (for that one project) are:
- MSSQL 7.0
- NT 4.0
- Apache 1.39
- used PHP 3.0.14, now switching to 4.0b4
- change source myself
- am actively changing PHP's ODBC functions
- compile myself, obviously
- MS Visual C++ 6.0
- I'll read all emails on this topic (PHP and ODBC in subject), but
if out of time I'd rather fix code than reply individually
Some of my agenda:
- Having written my code for PHP 3 I am not taking it over to PHP 4.
(Specifically support for calling SQL (stored) procedures and
getting output parameters back, and multiple result sets,
improved handling of large text.)
- For PHP 4 I made closing a connection also close a result
(works if there is only one result open at a time for one connection,
which I think might be all the time), in case people forget.
Some of the issues I think might be coming up:
- For myself I have added some more error checking, which is good,
but could scare people whose PHP / SQL code causes those errors;
mine were all quickly fixable in PHP or SQL
- there might be different behavior on Windows vs. Unix,
MSSQL vs. Oracle, Apache vs. IIS, cgi exe vs. module,
regular vs. persistent connection etc.
I'd like to know who uses it how much, to have better confidence whether we cover most versions
of systems in use.
- Leo Baschy <nirvana@got.net>