Base64 is about encoding not hashing... So decoding it is... natural. The point here is that it's integrated inside ChatGPT? It seems to me that it's an "obvious" "feature" kind of.
https://blog.sqlauthority.com/2010/05/14/sql-server-find-mos...
https://learn.microsoft.com/en-us/sql/relational-databases/p...
It's a bit weird but I'm using a langage (for a specific project) where prepared statements aren't available (except if you pay or use a specific DBMS, I can't do both because the client won't pay and I need SQLServer).
My initial idea was to use a DLL from PDO (I'm developping on a Windows env) or whatever known piece of code that is trustable in order to sanitize user inputs (of course we do it client side but user is devil :-)) before sending it to SQLServer.
After all answers and my researches, I think that I'll use a tiers piece of code to escape queries (probably a C# program using SQLCommand).
Thanks all.
If anybody knows exactly how SQLServer is handling SQL Statements, please let us know.
Converting that back to the query string you sent may be impossible because that structure won’t record comments, line breaks, indents, escaped characters and the like.
Converting it to a query string that, when sent back, produces the same internal structure should be possible, but as user selecsosi wrote “Most of this I would expect to be more on the client side than server”.
It makes sense.
I didn't catch the "client side" part as you do, thanks for the explanation.
"The string returned by sqlite3_expanded_sql(P) [...] is obtained from sqlite3_malloc() [...]"
From SQLite documentation: https://www.sqlite.org/c3ref/expanded_sql.html
https://www.psycopg.org/docs/cursor.html#cursor.mogrify
Most of this I would expect to be more on the client side than server (though w/ sqlite you are working w/ both)
I'm still wondering why it's not available for SQLServer (because there are use cases for this feature).
It is "just" a matter of driver interface (I mean the piece of code that implement ODBC API) that "just" do not give this feature or it's letteraly not possible with SQLServer?