rzo1 commented on PR #142: URL: https://github.com/apache/openjpa/pull/142#issuecomment-4373337761
> In that case, I think we should let it be. Maybe the TCK db leads to these errors. The alternative would be opening a challenge agains the TCK, but I guess they are past it (working on JPA 4 or 4.1). @tandraschko, to you agree? Realistically, we'd first need to identify something in the spec or TCK that supports the related claims, i.e. that something is off with the TCK schema definition. Once we have that, we can certainly raise a challenge though the process is fairly cumbersome in my opinion. We went through it a few times with TomEE and it was quite long. That said, if we're concerned about it, we could gate the override behind a TCK compatibility flag. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
