[CONJ-271] ResultSet.first() - SQLDataException: Current position is before the first row Created: 2016-03-30 Updated: 2016-04-07 Resolved: 2016-03-30 |
|
| Status: | Closed |
| Project: | MariaDB Connector/J |
| Component/s: | Other |
| Affects Version/s: | 1.4.0 |
| Fix Version/s: | 1.4.0 |
| Type: | Bug | Priority: | Critical |
| Reporter: | sfahren | Assignee: | Diego Dupin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | Current, ResultSet, first(),, position, | ||
| Environment: |
eclipse mars, mariaDB 10.1.13, Con/J 1.3.7 and 1.4.0 beta 1 |
||
| Attachments: |
|
| Description |
|
In the 1.4er Version it give a SQLDataException when calling ResultSet.first() to a executeQuery if the database (excepted the table) has no entries. The description in the javadocs says: in 1.4.0 beta 1 it returns also true, if no entry available. java.sql.SQLDataException: Current position is before the first row |
| Comments |
| Comment by Diego Dupin [ 2016-03-30 ] |
|
Resolved with commit : https://github.com/MariaDB/mariadb-connector-j/commit/318ca2483f34df6e2f9a81188e49c1256ebecf65 Thanks for reporting it. |
| Comment by Greg Huber [ 2016-04-07 ] |
|
Hello, I am using quartz scheduler and get this error when upgrading to 1.4. (1.3.7 works OK). Any ideas? 2016-04-07 14:38:40,946 ERROR org.quartz.core.ErrorLogger ErrorLogger:schedulerError - An error occurred while scanning for the next triggers to fire. |
| Comment by Diego Dupin [ 2016-04-07 ] |
|
Hi Greg Huber , i've created the |