Re: [PHP4BETA] odbc_close

At 11:10 AM 3/12/00 -1000, you wrote: >I have commented out odbc_close using php4 because it seems to >give an access violation. NT 4.0 IBM HTTP Server (apache). >Everything then runs fine. Is there still supposed to be a >problem with odbc? I'm using the php4 dev5 If that works for you that's good, keep it that way. Problems occur if you like me use odbc_close() on purpose. I'm taking ODBC very far, including actually having written for PHP3 code that gives me output parameters of procedures (odbc_procedure) and multiple result sets (not just rows) etc (also something you have asked for). Works fine in PHP3 and now bringing it into PHP4 and releasing it at the same time (releasing for PHP4 only, PHP3 is dead for me). While doing that I notice that some things in php_odbc of PHP4b4+ are less than perfect (some even don't work), and that's what much of this discussion is about. Great as the new Zend is, not every implication of Zend on php_odbc seems to have been thought of, by not any party (including myself, but I'm catching up quickly). The current public discussion of php_odbc on this list is to make sure Windows and Linux people are heard as well as people with different uses. Myself I have some pretty big PHP scripts that access many tables (possibly more than one database) for one page and do quite a lot of processing for one page, so I really use different features than others who e.g. serve lots of small data (which I do on a few pages only). You ask: Is there supposed to be a problem with php_odbc? I think if a user takes PHP3 script and it crashes unless she removes odbc_close() that _is_ a problem. Use it, it soon will be better than PHP3. - Leo Baschy <nirvana@got.net>