https://github.com/marschall/state-of-jpa-310

tests for the state of JSR-310 support in JPA providers
https://github.com/marschall/state-of-jpa-310

java jpa jsr-310

Last synced: about 1 month ago
JSON representation

tests for the state of JSR-310 support in JPA providers

• Host: GitHub
• URL: https://github.com/marschall/state-of-jpa-310
• Owner: marschall
• Created: 2018-04-22T13:31:36.000Z (over 6 years ago)
• Default Branch: master
• Last Pushed: 2024-06-14T10:12:24.000Z (6 months ago)
• Last Synced: 2024-06-14T11:34:54.992Z (6 months ago)
• Topics: java, jpa, jsr-310
• Language: Java
• Size: 91.8 KB
• Stars: 4
• Watchers: 3
• Forks: 1
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
State of JSR-310 Support in JPA

===============================

This project contains of tests for the state of JSR-310 support in JPA 2.2 providers.

The following databases are tested:

 * DB2

 * Derby

 * Firebird

 * H2

 * HSQLDB

 * MariaDB

 * MySQL

 * Oracle

 * PostgreS

 * SQL Server

The following JPA providers are tested:

 * EclipseLink

 * Hibernate

Currently none combinations pass.

Currently the tests focus on three areas:

 * avoid DST transition issues for `LocalDateTime`

 * support for keeping the offset in `OffsetDateTime`

 * nanosecond resolution for `LocalTime`

The 2nd level cache has been disabled to make sure entity are actually read from the database.

Accommodations have been made for the following database limitations:

 * Firebird only supports 100 microsecond resolution.

 * MySQL, MariaDB, Derby and Firebird do not support `TIMESTAMP WITH TIME ZONE`.

 * Oralce does not support `TIME`.

 * PostgreS, MySQL, and MariaDB only supports microsecond resolution.

 * PostgreS converts time zones to UTC when storing.

 * SQL Server only supports 100 nanosecond resolution.