Some help needed, will pay 200 dollar on paypal for first working example

[PeterNierop]

Dear all,

I feel noob again. I write C most of my life and MSSQL stored procedures.

Recently I looked at Rust and like what I see. However... the tears, the screams of agony.. i bolted the door to my 16th floor balcony... I might cut myself at least twice a day just because I am sure it would work in C ... and not in Rust.

So, i have this problem that needs a solution. Hence my offer.
Imagine a simple UPD server. It gets a simple bigint. Imagine a lovely MSSQL server that is willing, nay eager to do something beautiful with the bigint.
The problem... how to do that with Rust. I would enjoy a pool, however just a connection is fine. It be nice if it is async, but that is not required either. We might have multiple threads but that too is not needed. Just grab the bigint and toss it to SQL. Remember it is a stored procedure, not a query. Every time the UDP server gets another bigint... same thing, so it should loop or stay listening.

Seems simple right...

So, first to provide a sample that works... i pay you 200 dollar for beer, dinner or whatever you like to use it for. And you have my gratitude.

Thanks in advance

[mehcode]

The MSSQL driver in SQLx is still (sadly) very much at an beta level of quality and completeness. If you need a more complete on in Rust, today, please consider using https://docs.rs/tiberius/0.5.15/tiberius/ instead.

[PeterNierop]

Thanks for making me feel slightly better. I was considering taking up another job... something with potatoes and cutting then in slices and selling them with some helping of mayonaise.
I guess I will stick with C for a little longer and whip up some ODBC something. Decent ideas behind Rust though.. i will be back when the potatoes run out.

[PeterNierop]

In fact on second thoughts... what would push the SQL implementation ahead? For sure only the sun goes up for free. What would it need to have a real world implementation level.
What I do most is use Stored Procedures in SQL, aka as far removed from ORM as possible. These stored procedures do all the logic, check whatever and from a few inputs generate a single result which can be an int to indicate success or fail, or can be a varchar string. I happen to write a fair bit in government/bank apps. So any select statements are just not allowed, no direct inserts/update/delete/referencing/create/drop/truncate either. Only execute some known procs which tend to log/check access/check business rules/check parameters/and do all the heavy lifting in a single place.
What would it cost me for you to push the SQLx to include that on first level support?

[aeshirey]

The MSSQL driver in SQLx is still (sadly) very much at an beta level of quality and completeness.

Does SQLx function with MSSQL at all? I've been unable to get an extremely simple POC working, and I'm not sure if this is PEBCAK or incompleteness of the crate:

let connection = mssql::MssqlConnectOptions::new()
        .host("myserver.database.windows.net")
        .username("my_user")
        .password("secret!")
        .database("mydatabase")
        .port(1433)
        .connect()
        .await?; // Error: Io(Kind(ConnectionAborted))

sqlx = { version = "0.5", features = [ "runtime-async-std-native-tls", "mssql", "tls" ] }