3 ms·

Although the doc talks about their own SQL dialect "YQL", it seems to be supporting PG SQL as a compatible layer. https://github.com/ydb-platform/ydb/tree/main

Although the doc talks about their own SQL dialect "YQL", it seems to be supporting PG SQL as a compatible layer. https://github.com/ydb-platform/ydb/tree/main/ydb/library/yql/sql https://github.com/ydb-platform/ydb/tree/main/ydb/library/yq... It's fascinating to see the PG's prevalence as the de-fact SQL standard.

isoprophlex 5y ago
imo having had to deal with oracle sql, teradata sql, mssql and mysql, postgres as a dialect is such a sane and consistent experience. Also the ecosystem... The official docs basically solve your problems without much fuss, you don't have to rely on horrible vendor-specific forums.
- awild 5y ago
  > The official docs basically solve your problems without much fuss, you don't have to rely on horrible vendor-specific forums. tdodbc also comes with examples that are so far beyond the scope of a normal persons usecase, they honestly just feel like some greybeard doing the equivalent of a 10 minute long Tony Hawk combo. It's just such a pain in the butt to use, we had to fight teradata all the way till very recently.
- fomichev3000 5y ago
  While you have a good point, I need to say that traditional databases and distributed databases differ in some points. For instance in YDB you can connect to any node of a database, it means that you need some kind of balancing (server side or client side). I'm not talking about SQL dialect right now, but rather how you connect to database and how you handle connection losses or node overloads. YDB SDKs have client side balancing feature to distribute load evenly across database nodes.
fomichev3000 5y ago
Postgres support is in progress actually.
- Meai 5y ago
  it would be nice especially for using an IDE like Datagrip to manage and explore the YDB db