I don't seem to be able to get a sensible value for the SQL Server Varchar Data Type.

AField = 'Hello World'. in database

// Swift Code
let afield = rows[0].column("AField")?.string
print("Field Value = (afield!)")

When run
Field Value = 楗摮睯

I noted in the code TDSData+String.swift a Todo label -
// TODO
switch self.metadata.dataType {
case .charLegacy, .varcharLegacy, .char, .varchar, .nvarchar, .nchar, .text, .nText:

If (pretty please), this could be resolved that would be fantastic. I would then have a solution I could use.

Swift Metrics 2.0 just got released. It is almost completely compatible with Swift Metrics 1.x unless you exhaustively switch on the TimeUnit enum. I would highly recommend depending on swift-metrics like the following:

// swift-metrics 1.x and 2.x are almost API compatible, so most clients should use
.package(url: "https://github.com/apple/swift-metrics.git", "1.0.0" ..< "3.0.0"),

alternatively, from: "2.0.0" will also work but may in the interim cause compatibility issues with packages that specify from: "1.0.0".

If at all possible, this should be done before tagging the next release here. If using "1.0.0" ..< "3.0.0" this isn't even a SemVer major change because 1.x versions are still accepted.

I'm trying to connect to a SQL Server 2018. I can get it working from sqlcmd but I have to ignore the server's certificate trust.

When using swift-tds, I don't have this ignore certificate trust option, and I get -

error swift-tds : Uncaught error: handshakeFailed(NIOSSL.BoringSSLError.sslError([Error: 268435581 error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED]))

Is it possible we can do something like this -

i.e add an extra parameter on login to ignore certificate
conn.login(username: xxxx,
password: yyyyy,
server:zzzzz, database,
** tlsConfiguration: forClient(certificateVerification: .none)) **

Got the idea from this ---
app.databases.use(.mysql(hostname: host, port: port, username: user, password: pass, database: name, tlsConfiguration: ** forClient(certificateVerification: .none)),** as: .mysql)

Taken from this article -
https://forums.swift.org/t/fluent-connect-mysql-8-failure-how-to-solve/35939/14

I've been reviewing your library and I was wondering if you have any contribution guidelines?

I think I could enable iOS support fairly easily with the latest NIO. I also think I could implement RPC which is something I could use for a project I would like to try.

Cheers
Jordan

Basic Protocol Implementation

Below is a high level checklist for tracking the status of the TDS protocol implementation. It will be modified as necessary and may have parts moved to a future milestone as the initial goal is to end up just past the "proof of concept" phase:

Client Messages

• Pre-Login (Including SSL negotiation)
• Login
• Federated Authentication Token
• SQL Batch (Partially Implemented)
• Bulk Load
• Remote Procedure Call
• Attention
• Transaction Manager Request

Server Messages

• Pre-Login Response
• Login Response
• Row Data (Partially Implemented)
• Return Status
• Return Parameter
• Response Completion
• Error and Info
• Attention Acknowledgement

Token Parsing (Partially Implemented)

• ALTMETADATA (Deprecated in TDS 7.4)
• ALTROW (Deprecated in TDS 7.4)
• COLINFO (TDS 7.4+)
• COLMETADATA
• DATACLASSIFICATION
• DONE
• DONEINPROC
• DONEPROC
• ENVCHANGE
• ERROR
• FEATUREEXTACK (TDS 7.4+)
• FEDAUTHINFO (TDS 7.4+)
• INFO
• LOGINACK
• NBCROW (TDS 7.3.B+)
• OFFSET (Removed in TDS 7.2)
• ORDER
• RETURNSTATUS
• RETURNVALUE
• ROW
• SESSIONSTATE
• SSPI
• TABNAME
• TVP_ROW