Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jpa-dev] Question about TCK testing and different database server backends?

I haven't yet seen any new Persistence TCK tests that require DDL/DML script changes but am thinking that we could see a need for validation of each of the different database backends.  I'm just trying to understand who in the community will run the Jakarta Persistence 3.1 TCK tests for each of the database servers other than #2 Derby which has test coverage already. 

My responsibility is more on the Platform TCK (https://github.com/eclipse-ee4j/jakartaee-tck) but I need to understand how the Jakarta Persistence community will test each of the below mentioned databases (or not).  More specifically, which databases will still be supported by Persistence 3.1?  Will any of the databases be removed?  Will any new databases be added?  Also what does it mean exactly for someone to volunteer to test a certain database? 

In case it helps, https://db-engines.com/en/ranking/relational+dbms shows a ranking based on https://db-engines.com/en/ranking_definition

On 9/3/21 2:21 PM, Dmitri Cerkas via jpa-dev wrote:
If you need help I can assist you. 



On Friday, September 3, 2021, 08:13:45 PM GMT+2, Scott Marlow <smarlow@xxxxxxxxxx> wrote:


Hi,

Does anyone plan to run TCK testing with any of the [1] Database servers?  [1 is just a list of the Jakarta Persistence TCK scripts folders for each database back end, I hope that the folder names are obvious as to which database they represent.  For easy reference the names + links that I think they represent are:

  1. db2 (https://www.ibm.com/products/db2-database)
  2. derby (https://db.apache.org/derby)
  3. mssqlserver (https://www.microsoft.com/en-us/sql-server)
  4. mysql (https://www.oracle.com/mysql)
  5. oracle (https://www.oracle.com/database/technologies)
  6. pointbase (https://en.wikipedia.org/wiki/PointBase)
  7. postgresql (https://www.postgresql.org)
  8. sybase (https://www.sap.com/products/sybase-ase.html)

Any suggestions for how we can coordinate exactly whom to expect will validate each of these database backends as working with Jakarta Persistence 3.1 before the 3.1 release completes?  Perhaps no DDL/DML script changes are needed but even still, I think we need to understand which backends are used for Persistence TCK testing and perhaps which ones can be removed (until someone steps up to validate them for 3.1 or later).

Thoughts?

Scott

[1] https://github.com/eclipse-ee4j/jakartaee-tck/tree/master/sql

_______________________________________________
jpa-dev mailing list
jpa-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jpa-dev

_______________________________________________
jpa-dev mailing list
jpa-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jpa-dev

Back to the top