Skip to content

Conversation

@vpavic
Copy link
Contributor

@vpavic vpavic commented Aug 15, 2016

This PR adds Spring Batch configuration validation that disables database initializer in case custom table prefix is configured with default schema.

Related: #6649

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Aug 15, 2016
@vpavic vpavic force-pushed the improve-batch-autoconfig branch from a2f725a to bfa5fe4 Compare August 15, 2016 08:12
This commit adds Spring Batch configuration validation that disables database initializer in case custom table prefix is configured with default schema.
@vpavic vpavic force-pushed the improve-batch-autoconfig branch from bfa5fe4 to e43c6ed Compare August 17, 2016 21:24
@vpavic
Copy link
Contributor Author

vpavic commented Aug 18, 2016

I've updated the PR according to feedback from #6649.

@snicoll snicoll added type: enhancement A general enhancement and removed status: waiting-for-triage An issue we've not yet triaged labels Sep 11, 2016
@snicoll snicoll added this to the 1.4.1 milestone Sep 11, 2016
@snicoll snicoll self-assigned this Sep 11, 2016
snicoll pushed a commit that referenced this pull request Sep 12, 2016
This commit adds Spring Batch configuration validation that disables
database initializer in case custom table prefix is configured with
default schema.

See gh-6651
@snicoll snicoll closed this in ee668e6 Sep 12, 2016
snicoll added a commit that referenced this pull request Sep 12, 2016
* pr/6651:
  Polish contribution
  Validate Spring Batch database initializer configuration
@vpavic vpavic deleted the improve-batch-autoconfig branch September 12, 2016 12:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: enhancement A general enhancement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants