Hi,
It also might be worth remembering that the MySQL/Postgres Client, while very awesome, is a "technical preview", and may not be fully suitable for mission critical apps (or maybe it is, I don't know). I have been toying with the MySQL client and so far so good.
-Adam
On Monday, August 8, 2016 at 10:30:46 AM UTC-4, Thomas Segismont wrote:
Hi,
Actually, there are two options, JDBC Client and MySQL/Postgres Client. SQL common describes a connection object, which is the resource you need to execute queries. It is implemented by both the JDBC and MySQL/Postgres modules.
The JDBC client module let you use any JDBC compliant driver with Vert.x. It wraps JDBC calls with an asynchronous programming interface. But under the covers it uses worker pools (because JDBC is a blocking API).
MySQL/Postgres however uses this non blocking client:
https://github.com/mauricio/postgresql-async.
Regards,
Thomas
I trying to understand from the documentation what the best way is to access a Postgres database. I found three options (JDBC Client, SQL common and MySQL/PostgreSQL client) but I can't understand what the difference is. Any clues on which one to choose?
--
You received this message because you are subscribed to the Google Groups "vert.x" group.