mirror of
https://github.com/dimitri/pgloader.git
synced 2025-08-08 07:16:58 +02:00
Namely the actions are “keep extra” and “drop extra” and the casting rule guard is “with extra on update current timestamp”. Having support for those elements in the casting rules allow such a definition as the following: type timestamp with extra on update current timestamp to "timestamp with time zone" drop extra The effect of such as cast rule would be to ignore the MySQL extra definition and then refrain pgloader from creating the PostgreSQL triggers that implement the same behavior. Fix #735. |
||
---|---|---|
.. | ||
f1db-data.load | ||
f1db.circuits.my.sql | ||
f1db.circuits.pg.sql | ||
f1db.load | ||
history.sql | ||
my.load | ||
my.sql | ||
README.md |
pgloader tests for MySQL
The idea here is to create a MySQL database with a static known set of data so that we may then compare the data against a PostgreSQL load done with pgloader.
This is very much WIP at the moment, but at least it got started.