Re: Use pgloader with FDW

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Patricia DECHANDOL <pdechandol(at)intercountry(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Use pgloader with FDW
Date: 2018-03-23 12:51:49
Message-ID: 9fdea26e-b84d-f171-d403-59cfd988fbda@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 03/23/2018 03:55 AM, Patricia DECHANDOL wrote:
> Hello,
>
> I’m new to Postgresql and try to use the FDW with mysql database.
>
> Everything is OK to create my FDW and foreign tables, but I meet a
> problem when I try to do a select on a FOREIGN table containing datetime
> column which contains the value “0000-00-00 00:00:00” in mysql.

That is MySQL's version of NULL for datetimes. It is not a valid
datetime though.

>
> Select on the foreign table fails.
>
> The mysql datetime column has been automatically wrapped to “timestamp
> without timezone” column in the foreign table by the instruction “import
> foreign schema” that I used.

>
> How can I deal with this ?

https://github.com/EnterpriseDB/mysql_fdw/issues/38

>
> I read about the pgloader with can manage this king of problem, but
> can’t figure out how to use it with FDW.
>
> Thanks for your help.
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Patricia DECHANDOL 2018-03-23 13:07:47 RE: Use pgloader with FDW
Previous Message rob stone 2018-03-23 11:43:01 Re: Foreign Key locking / deadlock issue.... v2