When mapping a column with java type String and using jdbcType="NVARCHAR" in the @Column annotation we receive an error that the type is not supported by our H2 datastore. We looked at the H2Adapter a

Yes H2 does indeed claim support for NVARCHAR: https://h2database.com/html/datatypes.html?highlight=NVARCHAR&search=NVARCHAR#varchar_type But it fails to expose it via it's JDBC driver as supported JD

A committer on the H2 project suggested that "Actually JDBC metadata is not a reliable source of information in all or almost all drivers, don't trust it.". [1] Maybe the person is right and we should

Thanks for your support, below works for us. SQLTypeInfo sqlType = new H2TypeInfo( "NVARCHAR", // String typeName (short)Types.NVARCHAR, // short dataType 2147483647, // int precision "'", // String l

Interesting outcome in the discussion with Evgenij, H2 accepts NVARCHAR but doesn't directly support it. You can use it in H2 DDL though, will just be converted to VARCHAR. Wondering if it would be be

Ok, thanks Andy! Will change the local type as suggested.

I have a javax.validation.Min annotation on an Integer field in my JDO entity @Column(allowsNull = "true") @Min(0) @Getter @Setter private Integer scale; The generated Q code for this field is this, a

I'm getting the below error (rather "randomly') when loading certain fields of my entities. I don't know where to start looking. Any kind of advice is appreciated. On DN 5.2 with SQL Server. Let me kn

Wondering about that bit, is this an indicator that the field was loaded previously and has been unloaded? Under which circumstances would that happen? And why does reloading the field fail?

Thanks Andy. Does this mean we should try to load these fields eagerly? It also seems this only happens under higher load. What would be a good place to start looking for why this exception is being t

Thanks, Andy. It turned out this (and other strange "effects") was seemingly caused by the L2 cache. When we disabled it it went away.

Yes, well aware, and I will dig deeper into it, since we would like to re-enable L2 caching. Another issue we observed when using the L2 cache in our Apache Isis app was that sometimes (?) when an obj