Unsupported SET option client_min_messages
pietersv opened this issue · comments
Falcon looks amazing. Attempting to connect to a Vertica instance using the PostgresQL connection type. It almost works but fails on an unsupported option:
Unsupported SET option client_min_messages
Is Vertica support in the dev pipeline? Alternatively is it possible to note and proceed when some options aren't set? Usually Postgres drivers work fine with Vertica but not all newer Postgres options are supported.
We've already opened issue #344 to track the development of a connector for Vertica. As far as I know, no one has started to work on this issue.
I've quickly looked into the possibility of using the PostgresQL connector to connect to Vertica. And it seems this isn't possible without developing a new dialect for sequilize. There was an attempt here, but it's now closed.
As I mentioned in #344, node-vertica, although unmaintained, seems a feasible option.
Writing a connector based on node-vertica is a good first-issue to contribute to Falcon. If anyone steps in, we (the maintainers) will help.
Closing in favour of #344
It does appear a sequelize dialect for Vertica is the right way to go. I was able to get a good part of the way by commenting out a number of Postgres-specific settings, but the way it stores type information in systems tables is slightly different.
@pietersv The sequelize route sounds like more work than node-vertica. First, we'd have to contribute the new dialect to sequelize, and then implement the connector in Falcon. Despite having said that, I have no preference.
@n-riesco I think you're right. Will go that route. Thanks!