You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently maintain both "legacy" non-PDO DBConnectors and PDO based DBConnectors. This adds to our maintenance burden for less eddicient DB drivers.
It also makes improving performance more tricky as often the non-PDO based drivers won't implement features that help us be a bit more intelligent about what we pull out from the database - this can be a problem with seeking.
If we merge the patch @kinglozzer has written in #6501 there will be significant performance penalties for using non-PDO drivers as it is.
The text was updated successfully, but these errors were encountered:
I suppose we’ll need to consider whether PDO drivers come installed with PHP, and how hard it is to install them if not. I’d also weigh that up against whether devs already need to install extra software for other drivers anyway.
If we merge the patch @kinglozzer has written in #6501 there will be significant performance penalties for using non-PDO drivers as it is.
Just to clarify: in the context of that PR, SQLite3 is the one that suffers performance-wise currently, and MSSQL won’t work at all without some changes (to implement seek()). MySQL & PostgreSQL are both fine.
Edit: this issue is no longer relevant for the linked PR, but still should be considered IMO.
We currently maintain both "legacy" non-PDO
DBConnector
s and PDO basedDBConnector
s. This adds to our maintenance burden for less eddicient DB drivers.It also makes improving performance more tricky as often the non-PDO based drivers won't implement features that help us be a bit more intelligent about what we pull out from the database - this can be a problem with seeking.
If we merge the patch @kinglozzer has written in #6501 there will be significant performance penalties for using non-PDO drivers as it is.
The text was updated successfully, but these errors were encountered: