GenericDAO lastmod_on on update does not work about sabi HOT 2 CLOSED

Analysis so far of this hard nut:

1. created_on has never worked through the genericDAO Mapping but through database schema default setting.
2. genericDAO is working in principle but timestamp values are simply being ignored by JPA mapping.
3. I learned that LocalDateTime (java 1.8) was release after JPA 2.1 so there was no mapping for it. I upgraded spring-boot, and eclipselink level, such that we indeed use JPA2.2 now which says that LocalDateTime will be mapped to timestamp and vice versa as basic mapping.
4. I sponsored a genericDao Test, but this is lying, as it relies on the cache and does not see that the column is being ignored.
5. see branch sabi-22 for current state and use the rest API to reproduce the use case, instead of the junit.

Currently I assume that mariaDBs timestamp is not the same as mysqls timestamp and that eclipse links has difficulties because of this.
As long as the mapping does not work, a workaround would be to add a "on update current_timestamp" clause to the sql code. But this would surly mix up optimistic logging as soon as I want to enable this. Also if a entity is currently being fetched the columns are not mapped at all (i.e. created_on can not be accessed from java level).

very time consuming issue here - to be continued.

from sabi.

Basic conversion is working pretty well. Problem was cased because of having JPA Attributes within an Abstract Class which was not a mapped super class or something like this. So JPA simpy ignored it. Solution was to move the Tracable Attributes into en embedded type while leaving the tracable interface within the abstract class.

from sabi.