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
{{ message }}
This repository has been archived by the owner on Sep 28, 2022. It is now read-only.
postgreSQL and MySQL coroutines classes seem to have different methods (past parameters, return values, names...)
Too bad that these 2 classes allowing to query a database asynchronously do not use a common interface, at least for basic operations (connection, query, execute...).
To use these 2 classes and switch from one to the other within the same project (or framework), it is necessary to recode (in php) some wrapper classes, which is neither good for the time spent, nor for the performances.
postgreSQL and MySQL coroutines classes seem to have different methods (past parameters, return values, names...)
Too bad that these 2 classes allowing to query a database asynchronously do not use a common interface, at least for basic operations (connection, query, execute...).
To use these 2 classes and switch from one to the other within the same project (or framework), it is necessary to recode (in php) some wrapper classes, which is neither good for the time spent, nor for the performances.
But maybe I didn't find the right documentation, I only saw this :
https://www.swoole.co.uk/docs/modules/swoole-coroutine-postgres
The text was updated successfully, but these errors were encountered: