Jens Schauder

I think we got bitten by the JDBC API which seems to have a rather creative interpretation of dates. This [Stackoverflow answer](https://stackoverflow.com/a/14070771/66686) tipped me of. It talks about variants of...

While I think the JDBC API or SQL Servers driver implementation is using `Timestamp` wrong there isn't much of a point in bitching about this. But we can't really switch...

We'll probably implement some way to configure this. In the meantime you should be able to register custom converters for the conversion from and to `Timestamp`.

@Demo-80 please do not hijack only vaguely related tickets. Also, your question seems to be a usage question. Please ask those over on Stackoverflow. If you think you found a...

Please provide a [Minimimal Reproducable Example](https://stackoverflow.com/help/minimal-reproducible-example), preferable as a Github repository. Make sure to include the database, either as an in memory database or if that is not possible using...

I couldn't run your example but I was able to create some integration tests reproducing the problem. Although I can't reproduce that it actually works with H2. It does though...

As so often with dates there are more then one thing coming together here: 1. The problem you describe is probably related to really funny stuff the date conversion does...

The annotation should be '@InsertOnlyProperty' modelled after '@ReadOnlyProperty'.

Any implementation would currently only work for Aggregate Root properties. Therefore this has to wait until we have a better way of updating inner entities in place.

@taeyeon-Kim I'm confused by what the relation to the original issue is. Could you please clarify, or create a separate issue where you explain what the use case for such...