fix: Fixed DbmlExporter and other type Exporters to export DEFAULT consistently #654
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using dbmlExporter, if field.dbdefault.type is not set, a value of "DEFAULT " will appear. However, other Exporters will directly use field.dbdefault.type. I think it needs to be consistent.
.e.g:
MysqlExporter
OracleExporter
PostgresExporter
Summary
Issue
(issue link here)
Lasting Changes (Technical)
(please list down: code changes/things that have wide-effect; new libraries/functions added that can be used by others; examples below)
class EmailValidator
to validate email address' validity)Tenant#is_trial?
check)Checklist
Please check directly on the box once each of these are done