i habe a little problem, i'm using the 3.1 version an a debian machine with this little script:
LOAD DATABASE FROM mysql://<user>:<password>@localhost/gildamesh_test_db INTO postgres:///gildamesh_test WITH data only, truncate;
and i get this very strange error:
Error on Github
2017-07-03T07:17:33.101000Z ERROR Database error 22P02: invalid input syntax for type numeric: " "
CONTEXT: COPY per, line 1, column timezone: " "
Hello, I'm trying to find a way of casting a mysql
binary(36)to a postgres
uuid type, or, failing that, a
varchar(36). I'm frequently getting the error message:
2017-08-04T16:17:33.884000Z ERROR The value #(53 55 101 50 55 49 99 51 45 55 48 98 56 45 52 55 55 52 45 57 97 98 50 45 55 52 50 50 55 98 57 101 55 56 100 97) is not of type STRING
Does anyone know a way of casting the above using the options provided with pgloader, or do I have to write my own
using lisp function?
just tried to use pgloader from mssql:// into postgresql:// by compiling in debian-testing (hit issue #330) and with latest docker image the output is:
CORRUPTION WARNING in SBCL pid 1(tid 139666838079232): Memory fault at 0 (pc=0x7f06b75d6c3a, sp=0x7f06b7106e58) The integrity of this image is possibly compromised. Continuing with fingers crossed. KABOOM! FATAL error: Failed to connect to mssql at "192.168.10.200" (port 1433) as user "XXXX": Unhandled memory fault at #x0.
the part related to #330 is the alien sslv3 api usage.
libssl1.0.2(a lot of deps) and
libssl1.1(python3) installed so that might be the source of confusion (alien sslv3 api) ... I remember finding some discussion on
ironclad(or it's debian package) about the alien sslv3 api and it was a fixed issue. however I can't see how to get the build to use system installed
cl-ironclad(and I know nothing of the build chain)