issue with vertica odbc driver

phoebe · August 2017

Hi,

I meet a problem with Vertical ODBC driver. Version is 8.11 in linux.

When I call the ODBC API --GetInfo, the results opposite between linux and windows,

Below is the odbc trace from linux.
ENTER SQLGetInfoW
HDBC 0xae14e50
UWORD 10003 SQL_CATALOG_NAME
PTR 0x63f164bc
SWORD 1024
SWORD * 0x63f1792a

EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0xae14e50
UWORD 10003 SQL_CATALOG_NAME
PTR 0x63f164bc [ 1] "N"
SWORD 1024
SWORD * 0x63f1792a (1)

The result is "N" for "SQL_CATALOG_NAME in Linux while it returns Y in Windows

Any suggestion?

Thanks
Phoebe

sKwa · August 2017

Hi!

Just to be clear, you're asking about ODBC API? Might want to post this question on an unixODBC forum. They'll know better than we would.

phoebe · August 2017

Hi sKWa，

Thanks for your reply.
Is unixODBC sub category of vertica forum?

I am using HP Vertica ODBC driver, and the result of one ODBCAPI conflicts in windows and UNIX.
The ODBC driver is provided by vertica, so I raise the concern here.

Thanks
Phoebe

sKwa · August 2017

Hi!

Is unixODBC sub category of vertica forum?

No, unixODBC is an open source project that implements the ODBC API and its a separate project. I assumed you are using in unixODBC, but may be you are using in iODBC(who knows?), you did not describe environment.

I am using HP Vertica ODBC driver, and the result of one ODBCAPI conflicts in windows and UNIX.

You did not describe your problem/conflict, you just posted a diff of trace. Sorry, but its not a problem description. Could this be due to the OS's differences? I don't know, Im not an expert in low level ODBC API.

The ODBC driver is provided by vertica, so I raise the concern here.

But also exists a driver manager (unixODBC or iODBC) in this chain.

P. S.
Read this(just for example):Does anyone know how to set this to N since the default is Y?.

SQL_CATALOG_NAME is a v 3.0 facility

Vertica ODBC drivers conform to ODBC 3.5.1 specifications.

phoebe · August 2017

Hi sKwa,

Thanks for the input.

I am using progress DataDirect driver manager.

As the ODBC API returns different value between UNIX and WINDOWS.
I think it is a bug of Vertica ODBC driver?

Then how to create a bug to Vertica?

Thanks
Phoebe

sKwa · August 2017

Hi!

Then how to create a bug to Vertica?

You can do it via mail(but only if you are an enterprise customer). Mails` Subject & Body should be of a certain form, structured properly(i'm not sure its a public info, sorry). Try to ask your "seller"/"supplier", he should know how.

I am using progress DataDirect driver manager.

DataDirect 5.3 and 6.1 or later ? As I know its a proprietary driver manager.

issue with vertica odbc driver

Answers

Leave a Comment