laurenz
commented
8 years ago It works here (on 32-bit Windows and Linux) with the latest version from git, and I don't think that has changed since 1.4.0.
In Oracle:
SQL> CREATE TABLE datetest (
id NUMBER(5) CONSTRAINT datetest_pkey PRIMARY KEY,
d DATE
) SEGMENT CREATION IMMEDIATE;
SQL> INSERT INTO datetest VALUES (1, CURRENT_DATE);
SQL> INSERT INTO datetest VALUES (2, NULL);
SQL> INSERT INTO datetest VALUES (3, to_date('2100-01-01', 'YYYY-MM-DD'));
SQL> INSERT INTO datetest VALUES (4, to_date('100-01-01 BC', 'YYYY-MM-DD BC'));
SQL> COMMIT;In PostgreSQL:
test=> CREATE FOREIGN TABLE datetest (
id integer OPTIONS (key 'true') NOT NULL,
d date
) SERVER oracle OPTIONS (table 'DATETEST');
test=> SELECT * FROM datetest;
id | d
----+---------------
1 | 2016-05-20
2 |
3 | 2100-01-01
4 | 0100-01-01 BC
(4 Zeilen)NULLs should come across as NULLs.
- Can you provide the Oracle and PostgreSQL table definitions?
- Can you provide a self-contained test case that exhibits the behaviour?
- Can you verify in Oracle that the columns are indeed NULL?
fnicollet
Hello,
First of all, thanks a lot for your work on this project, it is incredibly useful :)
I am running latest PG 9.5 (9.5.3), using oracle_fdw-1.4.0-pg95-win64 that I downloaded from Github, with Oracle instantclient-basic-windows.x64-12.1.0.2.0. This is all running on my machine on Windows 10 64-Bits. I successfully used IMPORT FOREIGN SCHEMA but when I try to select one of the tables, I get the following error:
Means (in french) that the value is out of date/time bounds. The field of type DATE, nullable. And it does indeed contain some null values:
I looked at the issues and found some related to date encoding but fixed in the 1.4.0 changelog. I think it might be related to the fact that the value is null and not considered null during the "transfer" or something.
Thanks for your help, Fabien