Hi Benjamin,
This is unwanted inconsistency. Would you open a JIRA[1] issue? If not, I will
open one.
Maybe a DATETIME would be a better column type for MySQL.
Regards,
Milosz
[1] https://issues.apache.org/jira/browse/OPENJPA
> I think I may have uncovered a bug in the way TIMESTAMP fields a
I think I may have uncovered a bug in the way TIMESTAMP fields are generated
by the MappingTool.
I have a field
@Entity
public class MyEntity {
@Column(name = "due_date")
@Temporal(value = TemporalType.TIMESTAMP)
private Date dueDate;
In PostgresSQL, this generates a nullable TIMEST
