-
Notifications
You must be signed in to change notification settings - Fork 38.9k
Closed
Labels
in: dataIssues in data modules (jdbc, orm, oxm, tx)Issues in data modules (jdbc, orm, oxm, tx)type: enhancementA general enhancementA general enhancement
Milestone
Description
Benson Margulies opened SPR-7604 and commented
The EmbeddedDatabaseBuilder has a setName call. There is no corresponding attribute on jdbc:embedded-database. This is more than than esthetic: with 10.6.1.0 of derby, making two databases with the same name against a memory URL really only makes one, with rather unpleasant consequences reported elsewhere.
It has been suggested to use the beanId as the name instead of testDb; that would certainly patch the immediate problem even if a name= attribute would be nice.
Affects: 3.0.4
Attachments:
- mylyn-context.zip (2.67 kB)
Issue Links:
- Using multiple declarations of jdbc:embedded-database creates only one H2 instance per JVM [SPR-8920] #13560 Using multiple declarations of jdbc:embedded-database creates only one H2 instance per JVM
- Introduce support for generating unique names for embedded databases [SPR-8849] #13491 Introduce support for generating unique names for embedded databases
- Introduce database-name attribute in <jdbc:embedded-database /> [SPR-12835] #17432 Introduce database-name attribute in <jdbc:embedded-database />
Metadata
Metadata
Assignees
Labels
in: dataIssues in data modules (jdbc, orm, oxm, tx)Issues in data modules (jdbc, orm, oxm, tx)type: enhancementA general enhancementA general enhancement