News for hackers. Stuff that matters.
Re:Usql: v0.7.0 released by kenshaw on Wednesday June 13, 2018 @02:12AM (#17300673)
It's more of a passionate side project at the moment, as I am still reverse engineering the protocols involved. It's not close to completion, but I'm hoping to have it done sometime in the next few months. It's not a high priority, as there are other ways to connect to Oracle.

My goal is to get rid of all the non-Go dependencies, which would (for the first time, ever) finally make it a reality to have a single, small binary that can connect to "every" database and that can be freely distributed. If you'd like to help, please feel free to start an implementation. While I'm not following a specific development routine for the native Oracle driver, I do have a repository with a bunch of (non-building) code that I made to assist with inspecting the raw protocol captures.

Re:Usql: v0.7.0 released by grumpydba on Wednesday June 13, 2018 @03:25AM (#17301021)
Someone has already been there, the protocol is very.. rich, I would say:

https://blog.pythian.com/repost-oracle-protocol/

Re:Usql: v0.7.0 released by tracker1 on Wednesday June 13, 2018 @03:38AM (#17301074)
Hell, if that lead to Oracle drivers for other languages, that could be amazing too. It's nearly incomprehensible to me why Oracle hasn't documented their protocol.
Re:Usql: v0.7.0 released by emmelaich on Wednesday June 13, 2018 @06:14AM (#17301778)
Then it would difficult to change.

For instance to support clusters and failover.

Re:Usql: v0.7.0 released by grumpydba on Wednesday June 13, 2018 @07:42AM (#17302149)
MSSQL server protocol is documented and failover is handled. Protocol are usually versioned, or the initial handshake allows client/server capabilities negociation. Oracle has copyrighted a poem that the clients needs to send to make sure reverse engineered drivers are not possible: https://noss.github.io/2009/04/28/reverse-engineering-oracle...

Business as usual for Oracle and their horrible ethics...