note 124630 deleted from function.odbc-execute by cmb
| From: | cmb@php.net | Date: | Tue, 21 Jan 2020 06:57:26 +0000 |
| Subject: | note 124630 deleted from function.odbc-execute by cmb | ||
| References: | 1 | Groups: | php.notes |
| Request: | Send a blank email to php-notes+get-213930@lists.php.net to get a copy of this message | ||
Note Submitter: denemdenem at citromail dot hu
----
I've been working with PHP for only 1.5 years but it already prove numerous times that
it's outdated, badly supported and just generally an inconsistent and bad language. The
database drivers are the worst case.
You have sqlsrv, which is great, but only runs on Windows and after some hacking maybe on Linux/Mac
too. You have mssql, which is outdated just like odbc and the PHP "devs" didn't even
bother including it in new versions, but it supports stored procedure output parameters. And there
is odbc, which runs on everything. The catch? No option for in-out parameters.
Congratulations PHP. You don't care about your programmers and the driver writers don't
care about PHP and developers who have to put up with this awful language.
I have to write backend for Linux but in a Windows testing environment so it means I have to use
sqlsrv/mssql for the test code and mssql for the prod code. But then again, the server will be
updated by the admins to PHP 7 and I can say goodbye to stored procedures.
OR
Hack my way around and have the stored procedures write the result into a temporary table and then
run a table valued function to get the results. It can work, but at what cost? It's hacky,
unreliable (maybe the query doesn't run and you have no way knowing that) and plus lots of
hours rewriting code.
Thanks PHP, I hate you. I will try to avoid this devilish language at all cost in the future.