-
Notifications
You must be signed in to change notification settings - Fork 61
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
Timestamp values differ between oracledb and cx_Oracle #7
Comments
That SQL supplies no rows in my environment. Can you perhaps create a table with the data type (timestamp with time zone) and populate it with data so that we are using the same data? That would be helpful! |
This works for me:
with this Python code:
I get the expected output:
for both cx_Oracle and the new driver (both thick and thin). |
If I create a value with a timezone other than UTC I do see different results. I'll look into this further and get back to you. |
I see that GitHub automatically closes this when you mention in your commit comment that this issue is resolved. Please take a look and let me know if you agree. :-) |
The patch looks reasonable, but I'm not really qualified to judge that. When I try to follow the installation instructions at https://github.com/oracle/python-oracledb/blob/main/doc/src/user_guide/installation.rst#install-using-github It get:
However when I start with
I get a working |
Thanks for the confirmation. And thanks for the info about opensource.oracle.com. I get the same timeout - and also get it with cx_Oracle. I'll dig into it. |
This has been included in python-oracledb 1.0.1 which was just released. |
Continued from #2
Timestamps fetched by
oracledb
have different values that those fetched bycx_Oracle
. Usingalter session set time_zone
doesn't make a difference.The script
gives the following output on my machine:
I'm using
oracledb
in thin mode.The following Oracle related environment variables are set:
The text was updated successfully, but these errors were encountered: