-
Notifications
You must be signed in to change notification settings - Fork 82
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
Can't bind timestamp with timezone as string, time is not set #248
Comments
An obvious request: could you try the latest release 2.13.0? |
I took the lastest "nanodbc.h" and "nanodbc.cpp" from the repository at the master branch. Last modification on august 4 2020. I'm not sure of the version it is not written in the header file. |
There is no version macro, but there Line 1 in 7404a4d
Looks like the tests do not cover timestamp binding well, if at all, just nanodbc/test/postgresql_test.cpp Lines 233 to 236 in 7404a4d
I will try to look into that some time soon, but no timeline promises. |
Environment
Actual behavior
When you are binding a timestamps with timezone as a string, the time part is setted to 00:00:00.
For exemple if you are bindind "2020-09-03T15:27:38-02:00"
it will insert 2020-09-03T00:00:00 at the timezone of the database.
Expected behavior
When you are binding a timestamps with timezone as a string, the time should be the written one.
For exemple if you are bindind "2020-09-03T15:27:38-02:00"
it should insert 2020-09-03T15:27:38-02:00.
Minimal Working Example
`
//This is working
try
{
//This is not working
try
{
`
Results:
The text was updated successfully, but these errors were encountered: