rzo1 commented on PR #179: URL: https://github.com/apache/openjpa/pull/179#issuecomment-5529301822
Added `TestSchemaToolDroppedTables` (openjpa-jdbc, no database needed). The producer and consumer moved into two package-visible methods so the behaviour has a seam to test through, and it covers: - one persistence unit does not see another's drop, and clearing one leaves the other intact — the actual defect; - two factories of the same unit do share the tracking, so the `generateSchema()`-then-`buildSchema` flow keeps working; - a create forgets the entry, and outside spec-compliant mode the entry suppresses one create only; - the key falls back to the connection when a configuration has no id. The two partitioning cases fail if the map is collapsed back to a single global set, which I checked rather than assumed. Note the concurrency itself is still not covered: two persistence units initialising at the same time is not deterministically reproducible in a unit test, so the tests pin the partitioning that makes the interleaving harmless rather than the interleaving. -- 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]
