Regarding your original question, I have one in turn.
You are asking about the value of improving support for certain aspects of
the JDBC driver standard, having done a bit of searching to better
understand the features I'm now wondering if thats the wrong direction.
The reason being is that jOOQ seems to be focussed on providing the best
link between Java and the backend SQL data source, rather than directly
expose features of the JDBC driver standard. The issue I have can be best
seen with the following example I found on the net
try {
// Create a statement that will return updatable result sets
Statement stmt = connection.createStatement(
ResultSet.TYPE_SCROLL_SENSITIVE,
ResultSet.CONCUR_UPDATABLE);
//Primary key EmployeeID must be specified
//so that the result set is updatable
ResultSet resultSet = stmt.executeQuery(
"SELECT EmployeeID, Name, Office FROM employees");
} catch (SQLException e) {
}
So this shows the use of TYPE_SCROLL_SENSITIVE and CONCUR_UPDATABLE to allow
the generated result set to be updated.
>From a SQL/DBA's point of view this is nasty as the SELECT statement does not
>contain FOR UPDATE and so its rather hard to profile at
the DB server and/or debug issues. Instead the JDBC driver implements locking
without the visable tell tail in the SELECT statement.
Maybe for jOOQ the better option would be to implement updateable records based
on the use of FOR UPDATE within the SELECT statement,
so it remains SQL centric and an explicit choice by the developer that is
visable to any down stream DBA. This would also stop it
being over used by accident.
This also covers some other comments, such as the one from Joachim regarding
the loss of information - records maybe updatable if
the SQL allows them to be is better than making all records updatable if
fetched accordingly.
--
You received this message because you are subscribed to the Google Groups "jOOQ
User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
