Skip to content

Recommend using a single mechanism for schema generation #15859

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
wants to merge 1 commit into from

Conversation

m7stock
Copy link
Contributor

@m7stock m7stock commented Feb 6, 2019

Fixes gh-11721

Instead of trying to answer all specific questions, I'm trying to resolve the issue by giving a general advice in the documentation, see #11721 (comment)

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Feb 6, 2019
snicoll pushed a commit that referenced this pull request Feb 12, 2019
snicoll added a commit that referenced this pull request Feb 12, 2019
* pr/15859:
  Polish contribution
  Polish 'Database Initialization' section
@snicoll snicoll closed this in a1fbfbe Feb 12, 2019
@snicoll snicoll added type: task A general task and removed status: waiting-for-triage An issue we've not yet triaged labels Feb 12, 2019
@snicoll snicoll changed the title Schema generation approach notes Polish 'Database Initialization' section Feb 12, 2019
@snicoll snicoll self-assigned this Feb 12, 2019
@snicoll snicoll added this to the 2.1.3 milestone Feb 12, 2019
@snicoll
Copy link
Member

snicoll commented Feb 12, 2019

@MatthiasStock thank you for your contribution. I don't believe that this addresses #11721 though so we'll have to give it another look.

@wilkinsona wilkinsona added type: documentation A documentation update and removed type: task A general task labels Feb 12, 2019
@wilkinsona wilkinsona changed the title Polish 'Database Initialization' section Recommend using a single mechanism for scheme generation Feb 12, 2019
@wilkinsona wilkinsona changed the title Recommend using a single mechanism for scheme generation Recommend using a single mechanism for schema generation Feb 12, 2019
@m7stock m7stock deleted the gh-11721 branch November 9, 2019 18:46
@m7stock m7stock restored the gh-11721 branch November 9, 2019 18:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: documentation A documentation update
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Schema generation properties not well documented
4 participants