VAST 13.0 - Non-Unicode ODBC Connection uses Unicode ColumnNames
72 views
Skip to first unread message
thomas....@natural-software.eu
Dec 13, 2024, 3:24:44 AM12/13/24
to VAST Community Forum
Hello
We have a Non-Unicode ODBC Connection (MS/SQL Server) with a Non-Unicode Driver being accessed from AbtODBCDatabaseManager. However, the columnNames come back as Unicde Strings which messes with our mapping layer as we use Symbols to identitfy the connections.
Is there a way to prevent the column information to report the column name (NOT column type) as a "normal String" (as before)?
-- Thomas
Esteban A. Maringolo
Dec 18, 2024, 5:44:33 AM12/18/24
to va-sma...@googlegroups.com
Hi Thomas,
You should not get UnicodeStrings as column names. But I couldn't reproduce a situation where I would get such behavior.
The column name is obtained from an ODBC API call and the result is passed as a pointer to AbtOdbcDatabaseConnection>>#convertBufferToString:, only AbtOdbcUnicodeDatabaseConnection performs a conversion from UTF-16 to UnicodeString, the "regular"/ANSI version just converts the OSStringZ argument to a string using the active codepage.
Could it be that you created an ODBC connection with Unicode enabled and then disabled it at the manager level, but the Unicode connection is still registered under some alias? In such a case evaluating `AbtOdbcDatabaseManager shutDown` before doing anything should help.
Can you give me more details about the setup you have? E.g. MSSQL ODBC driver version, database collation configuration, if it happens to all column names or only to some of a specific table (and if so, can you share with us its schema?).
I'd appreciate this information so we can help you better, and remember that as a customer you can always get support from us by opening a ticket in the VAST Customer Portal.
Best regards.
The column name is obtained from an ODBC API call and the result is passed as a pointer to AbtOdbcDatabaseConnection>>#convertBufferToString:, only AbtOdbcUnicodeDatabaseConnection performs a conversion from UTF-16 to UnicodeString, the "regular"/ANSI version just converts the OSStringZ argument to a string using the active codepage.
Could it be that you created an ODBC connection with Unicode enabled and then disabled it at the manager level, but the Unicode connection is still registered under some alias? In such a case evaluating `AbtOdbcDatabaseManager shutDown` before doing anything should help.
Can you give me more details about the setup you have? E.g. MSSQL ODBC driver version, database collation configuration, if it happens to all column names or only to some of a specific table (and if so, can you share with us its schema?).
I'd appreciate this information so we can help you better, and remember that as a customer you can always get support from us by opening a ticket in the VAST Customer Portal.
Best regards.
| |||||||||||||||||
|
--
You received this message because you are subscribed to the Google Groups "VAST Community Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to va-smalltalk...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/va-smalltalk/5dd41649-68e8-4968-916b-d1111b7bc780n%40googlegroups.com.
thomas....@natural-software.eu
Dec 20, 2024, 1:33:38 PM12/20/24
to VAST Community Forum
Hello Esteban
Some more information:
It is MSSQL/ODBC Driver version 18 from Microsoft.
Database is according to the database guys Non-Unicode.
We have unicode disabled on Manager and Database level.
The system runs in a customer environment and they are out for the holidays. I´ll get back to you after Jan. 6th.
--Thomas
Reply all
Reply to author
Forward
0 new messages