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?


On 9/3/21 3:40 PM, David Matějček wrote:

Hi,

I can run something too. Just tell me what, when and HOW, prerequisities, because I never did this. Hmm, it seems well documented on GitHub, so ... I can try it when I find some time window for it.

Please see my previous response for more details of why I am asking.  Mostly, I am trying to understand if any Jakarta Persistence 3.1 changes are expected to the DDL/DML scripts under https://github.com/eclipse-ee4j/jakartaee-tck/tree/master/sql of the Platform TCK and who will be making those changes and who is validating that each file is correct.

Scott

(my experiences with databases: Informix (similar to DB2, but there are important differences!), Postgres, MySQL, MSSQL, Derby)

About removals - I know that EclipseLink contains some dialect customizations, so I would prefer to fix the implementation than removal of a backend. Another problems can cause some db server settings (large experiences with Informix and it's optimizations, memory settings, caches, etc.).

I can start with Postgres the following week, that should be the easiest one ... I would expect that the DB2 might be harder.

Coordination> I would create an issue for each database and then we can assign ourselves to the one we want to run (and give it a label "In Progress" to give a sign when we started with that)  :-)

David Matějček
On 03. 09. 21 20:21, 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


_______________________________________________
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