Skip to content

Create model for sql generation #1478

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
Tracked by #756
kurtn718 opened this issue Apr 5, 2023 · 1 comment
Closed
Tracked by #756

Create model for sql generation #1478

kurtn718 opened this issue Apr 5, 2023 · 1 comment
Assignees

Comments

@kurtn718
Copy link
Contributor

kurtn718 commented Apr 5, 2023

Create model for sql generation.

This model will represent the data for Sql generation in an abstract/generic representation. Separate tasks will take the model and generate SQL.

This task does include populating the model.

@kurtn718 kurtn718 self-assigned this Apr 5, 2023
kurtn718 added a commit that referenced this issue Apr 5, 2023
Initial model for generating schema SQL.

Closes #1478
kurtn718 added a commit that referenced this issue Apr 13, 2023
Initial Data Model for Schema SQL Generation that can generate SQL for a simple entity.

Closes #1478
@kurtn718
Copy link
Contributor Author

Changes for this are merged into feature branch

kurtn718 added a commit that referenced this issue May 20, 2023
Initial Data Model for Schema SQL Generation that can generate SQL for a simple entity.

Closes #1478
mp911de pushed a commit that referenced this issue Jun 6, 2023
We now support schema creation and schema migration by generating Liquibase changesets from mapped entities. We also support evolution of schema by comparing existing tables with mapped entities to compute differential changesets.

Closes #1478
Original pull request: #1520
mp911de added a commit that referenced this issue Jun 6, 2023
Reformat code, switch to tabs. Accept property in DatabaseTypeMapping to provide more context to the type mapping component.

Rename LiquibaseChangeSetGenerator to …Writer as we're writing a changeset and computing the contents is a consequence of writing a changeset. Refine naming to express what we're actually doing.

Introduce setters for enhanced configuration of predicates. Reduce visibility of types to avoid unwanted public API where public access is not needed.

Remove usused code, move methods around for improved grouping of code.

Rename package to schema as the schema is being created and updated and not generated. Rename …Model classes to just their name as types are package-private and not visible externally. Refactor SchemaDiff to Java record.

Use different overloads to write schema changes to avoid LiquibaseException leaking into cases where no diff is being used. Introduce SchemaFilter to filter unwanted mapped entities.

Move code to JDBC module. Introduce comparator strategy to customize how table and column names are compared.

See #1478
Original pull request: #1520
mp911de added a commit that referenced this issue Jun 6, 2023
See #1478
Original pull request: #1520
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant