Netezza support

[gracebrownecodes]

It seems like it would be fairly easy to add support for Netezza and there is an existing use case in PEDSnet. Since Netezza is based on PostgreSQL, I'm thinking it would be very similar to the redshift implementation in connect.default. Thoughts?

[schuemie]

I would like to continue this discussion in the forum.

[schuemie]

The Netezza-specific code looked harmless enough, so I merged it with the master branch and included it in the latest testing-round. No problems were found.

I would still recommend including the JDBC jar in the package if licensing allows.

[cgreich]

Friends: Trying to connect to Netezza. Your block of code doesn't seem to be working with our box:

• There is no such a command as "set search_path to". Instead, it should be "set schema to". Aaron must have installed some compatibility module or so.
• Actually, I would like to try to get around that. Instead of setting a search path or schema, I want to use the name in the queries. Why can't we do that. The syntax would be SELECT * FROM ... What's wrong with that?
  We need a solution for the vocabulary. What if it doesn't live in the same schema as the data table? Or is that a requiement.
  pbr6cornell commented 9 years ago

  Vocabulary tables are part of cdm and must be in the cdm_schema.

  Analysis scripts do use the 'use'/'set schema' function, and there are specific instances where it is necessary to do so (such as for checking existence of temp tables in oracle). On Feb 4, 2015 11:41 PM, "Christian Reich" notifications@github.com wrote:

  Friends: Trying to connect to Netezza. Your block of code doesn't seem to be working with our box:

  • There is no such a command as "set search_path to". Instead, it should be "set schema to". Aaron must have installed some compatibility module or so.
  • Actually, I would like to try to get around that. Instead of setting a search path or schema, I want to use the name in the queries. Why can't we do that. The syntax would be SELECT * FROM ... What's wrong with that?
  • We need a solution for the vocabulary. What if it doesn't live in the same schema as the data table? Or is that a requiement.

  — Reply to this email directly or view it on GitHub https://github.com/OHDSI/DatabaseConnector/issues/1#issuecomment-72993357 .

  ericaVoss commented 9 years ago

  @cgreich here we have a main Vocab that sits alone but we also embed the Vocab the CDM was run on within the CDM. This allows your main Vocab to update while you still maintain the exact copy that built the CDM.

  • © Githubissues.
  • Githubissues is a development platform for aggregating issues.

[pbr6cornell]

Vocabulary tables are part of cdm and must be in the cdm_schema.

Analysis scripts do use the 'use'/'set schema' function, and there are specific instances where it is necessary to do so (such as for checking existence of temp tables in oracle). On Feb 4, 2015 11:41 PM, "Christian Reich" notifications@github.com wrote:

Friends: Trying to connect to Netezza. Your block of code doesn't seem to be working with our box:

• There is no such a command as "set search_path to". Instead, it should be "set schema to". Aaron must have installed some compatibility module or so.
• Actually, I would like to try to get around that. Instead of setting a search path or schema, I want to use the name in the queries. Why can't we do that. The syntax would be SELECT * FROM ... What's wrong with that?
• We need a solution for the vocabulary. What if it doesn't live in the same schema as the data table? Or is that a requiement.

— Reply to this email directly or view it on GitHub https://github.com/OHDSI/DatabaseConnector/issues/1#issuecomment-72993357 .

[ericaVoss]

@cgreich here we have a main Vocab that sits alone but we also embed the Vocab the CDM was run on within the CDM. This allows your main Vocab to update while you still maintain the exact copy that built the CDM.