Skip to content
This repository has been archived by the owner on Dec 22, 2020. It is now read-only.

MoSQL::Schema::PGError (NameError) #133

Open
thejusss opened this issue Jul 10, 2018 · 4 comments
Open

MoSQL::Schema::PGError (NameError) #133

thejusss opened this issue Jul 10, 2018 · 4 comments

Comments

@thejusss
Copy link

Hi,

When I run the command mosql --collections collections.yml --skip-tail for importing data from Mongo db to Postgre, I am getting the following error.

`rescue in block in copy_data': uninitialized constant MoSQL::Schema::PGError (NameError)

SQL Tables are creating successfully. But the data is not imported.

Any idea about this issue?

@psantwani
Copy link

@thejusss, Were you able to make this work ?

@psantwani
Copy link

@thejusss I was getting the same error. I was using an unsupported data type called UUID in my collections.yml. Replaced it with CHARACTER VARYING and I was able to successfully import the data.

@sneerin
Copy link

sneerin commented Aug 26, 2019

from a performance perspective, UUID is much better comparing to CHAR, that's very important due to nature of MongoDB id.

@epaolillo
Copy link

Solved!
Just downgrade the 'pg' gem version to 0.21 version. The constants PGError and another similar are deprecated from 1.0.0 'pg' gem version.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants