Skip to content

Configure script execution behaviour of embedded database [SPR-8210] #12860

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
spring-projects-issues opened this issue Apr 5, 2011 · 1 comment
Assignees
Labels
in: core Issues in core modules (aop, beans, core, context, expression) status: duplicate A duplicate of another issue type: enhancement A general enhancement

Comments

@spring-projects-issues
Copy link
Collaborator

spring-projects-issues commented Apr 5, 2011

Ben Sion opened SPR-8210 and commented

It would be very helpful if the EmbeddedDatabaseBuilder could be configured to continue on error or ignore drop statements when executing schema and data scripts. This would simplify the use of the EmbeddedDatabase for use in unit tests (and probably other scenarios).

I have attached a patch for this issue. Basically a new constructor is added to the EmbeddedDatabaseBuilder taking in 2 booleans that configure the underlying DatabasePopulator's ignoreFailedDrops and continueOnError values.

I realise that I could create my own DatabasePopulator and execute the scripts outside of the EmbeddedDatabaseBuilder's initialisation but this seems like a lot of extra lines of code. Please let me know if I can provide more information.


Affects: 3.0.5, 3.1 M1

Attachments:

Issue Links:

@spring-projects-issues
Copy link
Collaborator Author

spring-projects-issues commented Nov 20, 2014

Sam Brannen commented

Resolving this issue as a Duplicate since the requested functionality has already been implemented in conjunction with #16037.

@spring-projects-issues spring-projects-issues added type: enhancement A general enhancement in: core Issues in core modules (aop, beans, core, context, expression) status: duplicate A duplicate of another issue labels Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) status: duplicate A duplicate of another issue type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants