Skip to content
This repository has been archived by the owner on Sep 28, 2022. It is now read-only.

Swoole coroutine Mysql & PostgreSQL public interfaces #11

Open
jcheron opened this issue Jan 4, 2020 · 2 comments
Open

Swoole coroutine Mysql & PostgreSQL public interfaces #11

jcheron opened this issue Jan 4, 2020 · 2 comments

Comments

@jcheron
Copy link

jcheron commented Jan 4, 2020

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

@sy-records
Copy link
Member

English documents are not synchronized, You may need to look at the examples in the Chinese documentation.https://wiki.swoole.com/#/coroutine_client/postgresql

@jcheron
Copy link
Author

jcheron commented Mar 3, 2020

The Mysql and PostgreSQL classes finally seem to have the same public interface.
Thanks @sy-records

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants