SQL : It is not possible to use an SQLUpdateClause which sets columns to expressions

[Luis Fernando Planella Gonzalez]

Currently, the update clause only have a .set(Path<T>, T), but with this, it is not possible to do things like "update t set a = a + 1"
I think we would need another method like .set(Path<T>, Expression<T>).
Maybe this should be supported in inserts as well (defined on the StoreClause). Maybe custom expressions which invokes db functions would work (like insert into x values (current_timestamp())).

[Timo Westkämper (timo-westkamper)]

I implemented that change in SVN trunk, but there is now the problem that set(someStringPath, null) calls are ambiguous and the compiler complains.

This can be fixed like this though :

set(someStringPath, (String)null)

Maybe an additional setNull(Path<?> path) could work. What do you think?

[Luis Fernando Planella Gonzalez (luisfpg)]

For me, both solutions would be fine: either having an extra setNull(path) or having a method with a different name, like setExpression(path, expression)

[Timo Westkämper (timo-westkamper)]

Fixed in SVN trunk :

set(Path<T>,T)

set(Path<T>, Expression<? extends T>)

setNull(Path<T>)

[Timo Westkämper (timo-westkamper)]

Released in 2.0.1