Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inserting datetimeoffset's using microsoft sql server produces inconsistent results #186

Closed
nicoleepp opened this issue Feb 14, 2018 · 3 comments

Comments

@nicoleepp
Copy link
Contributor

Example, when running locally:

julia> using ODBC
julia> dsn = ODBC.DSN("MSSQL-test", "SA", "YourStrong!Passw0rd")
julia> ODBC.execute!(dsn, "drop table if exists test1")
julia> ODBC.execute!(dsn, "create table test1 (test_datetimeoffset datetimeoffset)")
julia> ODBC.execute!(dsn, "insert test1 VALUES ('2016-01-01 01:01:01-05:00')")
julia> source = ODBC.Source(dsn, "select * from test1")
julia> data = Data.stream!(source, Data.Table)
(test_datetimeoffset = Union{Missings.Missing, ODBC.API.SQLTimestamp}[2016-01-01T00:01:01])

But when running the same thing on docker I get:

(test_datetimeoffset = Union{Missings.Missing, ODBC.API.SQLTimestamp}[2016-01-01T06:01:01])
@quinnj
Copy link
Member

quinnj commented May 24, 2020

Sorry for the delay in responding to this; is there a way you could try to reproduce this on master? A big refactor was just merged, so I wonder if things got tidied up enough to fix something like that.

@nicoleepp
Copy link
Contributor Author

Sorry I don't have the same setup as before so I'm not sure how to reproduce this anymore

@quinnj
Copy link
Member

quinnj commented May 26, 2020

Ah shucks; sorry for the delay and not following up on this sooner.

@quinnj quinnj closed this as completed May 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants