axibase / atsd-jdbc Goto Github PK

Need a section 'Build Driver' which outlines the steps involved in building the driver - with dependencies.

-- ping query
SELECT 1

Result:

Error while executing SQL "-- ping query
SELECT 1": Unsupported statement type: --```

Driver version 1.4.8 (we don't have 1.4.9 on maven)

SELECT tags.symbol, tags.class_code, tags.lot AS LONG FROM atsd_entity WHERE tags.symbol = 'LKOH' limit 1

The third column getColumnTypeName returns varchar, ignoring the cast.

Server metadata is:

"tags.symbol","tags.class_code","LONG"
"LKOH","EQRD","1"

See tests:
https://github.com/axibase/atsd-jdbc-test/blob/master/src/test/java/com/axibase/tsd/driver/jdbc/connectionString/TablesTest.java

After travis-ci shutdown, we don't have snapshot releases.

Integrate atsd-jdbc-test repo as a module and run integration tests in main repo on each pull request

Current implementation of PreparedStatement#getMetadata() in master uses /api/sql/meta without modifying the query. If the query contains placeholder symbols, ATSD returns error. How should this case be resolved?

• Cut the query starting with WHERE condition. It will help for some simple software-generated queries.
• Implement smart query processing in JDBC driver
• Support prepared statements in ATSD level
• Something other?

Check that input stream is always fully read and closed to prevent leaks

The readme needs to cover the case, that the same statement cannot be re-used to execute multiple queries.

Statement statement = connection.createStatement();
ResultSet resultSet1 = statement.executeQuery(query1);
while (resultSet1.next()) {
   //process resultset
}
ResultSet resultSet2 = statement.executeQuery(query2);

What error will be raised? What is the recommended pattern?
Actually, we could automatically close resultSet1 once we reach the last row to allow this kind of use case?