Renaming some Exasol specific JDBC and ODBC methods

Detail name	Value
Changelog Number	10239
Type	Improvement
Status	Resolved
Fix Versions	Exasol 7.0.0
Resolution Date	2020-09-11

Description

Beside the standard methods for ODBC and JDBC Exasol offers additional Exasol specific methods.

Improvement

Starting with Exasol Version 7 some of these Exasol specific methods got renamed.

JDBC

old name	new name
public boolean isSlaveConnection()	public boolean isWorkerConnection()
public boolean isSlaveConnection()	public boolean isWorkerConnection()
public int [] GetSlavePorts()	public int [] GetWorkerPorts()
public String [] GetSlaveHosts()	public String [] GetWorkerHosts()
public long GetSlaveToken()	public long GetWorkerToken()

in the class EXAConnection.

ODBC

old name	new name
SQLRETURN EXASlaveConnect()	SQLRETURN EXAWorkerConnect()
SQLRETURN EXAGetSlaveOffset()	SQLRETURN EXAWorkerConnect()

Changed behavior

We have renamed some Exasol specific JDBC and ODBC methods. This methods are used for parallel result set reading and parallel data insert into the Exasol database nodes. *JDBC* ||old name||new name|| |public boolean isSlaveConnection()|public boolean isWorkerConnection()| |public boolean isSlaveConnection()|public boolean isWorkerConnection()| |public int [] GetSlavePorts()|public int [] GetWorkerPorts()| |public String [] GetSlaveHosts()|public String [] GetWorkerHosts()| |public long GetSlaveToken()|public long GetWorkerToken()| in the class EXAConnection. *ODBC* ||old name||new name|| |SQLRETURN EXASlaveConnect ()|SQLRETURN EXAWorkerConnect ()| |SQLRETURN EXAGetSlaveOffset()|SQLRETURN EXAWorkerConnect ()|