note 111647 deleted from mysqlinfo.api.choosing by crell
| From: | crell@php.net | Date: | Mon, 04 Apr 2022 16:57:51 +0000 |
| Subject: | note 111647 deleted from mysqlinfo.api.choosing by crell | ||
| References: | 1 | Groups: | php.notes |
| Request: | Send a blank email to php-notes+get-218119@lists.php.net to get a copy of this message | ||
Note Submitter: michaeln at associations plus dot see eh
----
Another useful consideration to keep in mind when choosing your library is how extensible it is.
Chances are, in any sufficiently advanced development scenario, you're going to be extending
your database access class to add a method (or multiple methods) for how to handle database errors
and alert the development team of errors and whether to have the code fail immediately or fail
gracefully serving the user a user-friendly failure notice.
For example, I have a class where I have added extra parameters to the query() function (and a few
others), which accept the __FILE__ and __LINE__ constants to facilitate tracking issues. If this
were not reasonably possible with PDO-mysql for example (not sure, never used it), it may make one
option or the other much less likely to be viable for your usage case.