Quirks re-visited about sql2o HOT 5 CLOSED

Different projects have different type standarts|convections (VARCHAR vs NVARCHAR, CLOB vs NCLOB).

This could be solved by extracting the logic that translates column name into property name to an interface using strategy pattern. ColumnNamingStrategy or similar. The ColumnNamingStrategy would be a part an Sql2o instance.

Different projects have different type standarts|convections (VARCHAR vs NVARCHAR, CLOB vs NCLOB).

Could you explain this better? I don't see what it has to do with the java code if you use CHAR type or NCHAR type in the database?

from sql2o.

Could you explain this better? I don't see what it has to do with the java code if you use CHAR type or NCHAR type in the database?

example: clobs are NClobs, Strings are NStrings:

setParameter(PreparedStatement ps, int index, String value)->ps.setNString(index,value);

from sql2o.

i.e. for same DB in different projects you need to call setNString|getNString
for other projects you need setString|getString

from sql2o.

I just want to say Quirks is not just DB-related but concrete JDBC-driver + project related

from sql2o.

I will closed this issue.
We can provide some common quirks implementations, but if developers have special needs, they will have to create their own quirks implementation.

from sql2o.