Re: [PHP4BETA] odbc_close

>lets try to keep this polite - Agreed. Please see anything I write as technical, not personal. In case of doubt consider people as peripheral devices that interact with code ;) >sorry, you're missing the point again - it's *not* about >odbc, it's about stability and design. Stability as consequence of good design is an agreed goal. But it is somewhat about ODBC. You must consider its needs, e.g. don't take its buffers away while it still expects them to be there, etc. And ODBC has a certain way of organizing and naming things, and if you consider those, as well as PHP's needs, you'll get a very nice design. >all the stuff i did for php crashes at least once a day;-) - >man, that's what it's all about. That's not what it is about. That happens, but I often spend hours going through code, and sometimes days rewriting code, just to come out with something that runs and runs and runs. I appreciate people who get things done quickly, but when I have a choice I spend time on making things very very reliable. Not judging one or the other to be better. But trying to clarify my approach. >you're targetign the wrong person. Not targeting anyone. I appreciate the efforts of everyone to have got PHP where it is. But as php_odbc as of PHP4b4 as I found it did _not_ work acceptably I had to look at it. Now I'm trying to make it work well. Anyway, too much email, not enough code ;) I am about to have "my modifications" ready for PHP4 (were running just fine under PHP3). Why don't I send them over to Thies and Andreas to look at. I guess I'd finish in a few hours from now. Then a day or two using it, then I'd send it over. Or do you want it sooner? I mean I have parts of it ready now, but I'd send the whole thing so you don't have to look twice, and in case I recognize mistakes. >so you're saying you want to write spagetthi-code Nope. I wrote some very general code that deals with databases and tables in a very general way so I won't have to rewrite too many lines if I change the databases. As part of that I put plenty of error and exception handling and optional optimizations in. And part of that strategy, dealing with reality, is to have odbc_close() calls. Again I'd like to mention the other big reason: License limit on connections can get tight in peak traffic. And last not least, a good reason to use the odbc_close() calls is in a project that involves several programmers on a Web site, PHP scripts being made of parts written by several people, where I don't want to check all of their code, but still want to clean up after them and guarantee the server to keep running well. - Leo Baschy <nirvana@got.net>