Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ODBC Query with NULL value

See original GitHub issue

System information:

Windows 10
DBeaver 6.1.1.201906240635
Java 11.0.3
Additional extensions: without

Connection specification:

Database: SQL
Driver name: JDBC
Do you use tunnels or proxies : ODBC Connection, SQL Anywhere 17

DBeaver returns NULL in fields where the value is 100%. The following is an example of query and table view:

LOG FILE:

!SESSION 2019-07-03 09:20:11.687 -----------------------------------------------
eclipse.buildId=unknown
java.version=11.0.3
java.vendor=AdoptOpenJDK
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en
Command-line arguments:  -os win32 -ws win32 -arch x86_64

!ENTRY org.jkiss.dbeaver.model 4 0 2019-07-03 09:20:24.000
!MESSAGE Error determining server version
!SUBENTRY 1 org.jkiss.dbeaver.model 4 0 2019-07-03 09:20:24.000
!MESSAGE 
!STACK 0
java.lang.UnsupportedOperationException
	at sun.jdbc.odbc.JdbcOdbcDatabaseMetaData.getDatabaseMajorVersion(JdbcOdbcDatabaseMetaData.java:4030)
	at org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCDatabaseMetaDataImpl.getDatabaseMajorVersion(JDBCDatabaseMetaDataImpl.java:140)
	at org.jkiss.dbeaver.model.impl.jdbc.JDBCDataSource.initialize(JDBCDataSource.java:348)
	at org.jkiss.dbeaver.ext.generic.model.GenericDataSource.initialize(GenericDataSource.java:426)
	at org.jkiss.dbeaver.registry.DataSourceDescriptor.connect(DataSourceDescriptor.java:785)
	at org.jkiss.dbeaver.runtime.jobs.ConnectJob.run(ConnectJob.java:70)
	at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:102)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

Query:

Issue Analytics

State:
Created 4 years ago
Comments:27 (3 by maintainers)

Top GitHub Comments

2reactions

rambouilletcommented, Aug 9, 2022

Change your NVACHAR to VARCHAR and everything will be visible. That’s how I did it on my project.

I would do this, but Entity Framework is preferring nvarchar over varchar, and I don’t want to change its default functionality. Plus, I would lose all the benefits of Unicode if I just used varchar.

2reactions

eramcommented, Sep 27, 2020

I’m getting the same issue with ODBC driver: CData for Azure Table Storage v 20.0.7515.0 DBeaver 7.2.1.202009201907