omerkirk

Thank you, will submit one today

Here is the setup I am using: ``` CREATE TABLE TEST_OCINUM_SCAN ( NUM NUMBER NOT NULL ); INSERT INTO TEST_OCINUM_SCAN VALUES (123456); ``` ``` ora.Cfg().Env.StmtCfg.Rset.SetFloat(ora.N) ora.Cfg().Env.StmtCfg.Rset.SetNumberFloat(ora.N) ``` Can you try...

There is probably very little we can do, I checked the convert.go from database/sql and types that are allowed to be converted to *string are restricted. Although I think any...

There are 4 issues at hand causing my problem here. 1- The column that should be an INTEGER is defined as NUMBER, so it is mapped to a float64 without...

I will try the master as soon as I can, will let you know

I see, is the "v4" branch only for go 1.8 or should I expect any breaking changes ? My current go version is 1.7.4.

I finally upgraded our go version to go 1.9 and tried the trick you mentioned above. It works great for numbers now, however if a number column is null the...

Yes you are right I just filed the issue since everything is working correctly in goracle.v1, but changed the query now and things are working ok in rana/ora.