ydb-platform / ydb-rs-sdk

Apache License 2.0
48 stars 16 forks source link

Is Ydb platform ydb-rs-sdk stalled? #181

Closed makorne closed 5 months ago

makorne commented 6 months ago

I posted a serious bug 3 days ago.. Nobody answered to it.

As was written here 2 years ago: If you know existed good migration tool - better add YDB support to it

But almost every in the rust world knows that this tool - sqlx .

And it was planned to Add support ydb to sqlx 2 years ago!!

And still nothing changed!

Ask your bosses: will users have to wait for basic migration tools for 5, 10 or 20 years? But users will lose interest in a so slowly developed sdk! May be bosses can find enough developers for normal developing speed?

The unoficial one-man project alone did migrations, pools and many of these useful things:

YQL Query for data (like DML)
YQL Query for sheme (like DDL)
Connect over grpcs (with tls)
Connect over grpc (without tls) - not worked, unknown cause
Connection pool (with [deadpool](https://crates.io/crates/deadpool)) (feature pool)
Token authentication
Service account key authentication (feature auth-sa)
Metadata authentication
Query helpers (a lot of)
[sqlx](https://crates.io/crates/sqlx) integration - partially done (feature sqlx):

    Connection string
    connection
    binding parameters
    preparing statements
    transaction manager
    DML (data) operations
    DDL (scheme) operations
    primitive types (bool, i8, i32, i64, u8, u32, u64, f32, f64, Vec<u8>, String)
    date types (Date, Datetime, Timestamp, Interval)
    Decimal type
    connection pool balancing for discovery
    compile-time checked queries
    migrations
    multiple transaction modes
    log statements
    operation parameters

Why can't a commercial platform develop even at the same speed as one man writing for free in his free time?

rekby commented 5 months ago

Hello.

Thanks for your feedback. It is important for us.

I posted https://github.com/ydb-platform/ydb-rs-sdk/issues/180 3 days ago.. Nobody answered to it.

It isn't a bug. You can configure timeouts with standard tokio's way: use timeouts. I agree about examples can be better.

We are working on the SDK, for example we have added support of new auth type and coordination service some time ago.