Added support for Oracle datatype. If you could refer to #797
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
July 30, 2018 18:25
….oracle.com/cd/E12151_01/doc.150/e12155/oracle_mysql_compared.htm#i1027526 on section 2.3.3.1, mediumint would be suggested as NUMBER(7,0) and mediumint does not exists in Oracle. INT gets tricky, as liquibase translate it as INTEGER. Oracle treats INTEGER as NUMBER(38,0) which is like a BIGINT or the maximum size support. Following the same documentation, it's probably best to be used as NUMBER(10,0).
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
https://docs.oracle.com/cd/E12151_01/doc.150/e12155/oracle_mysql_compared.htm#i1027526 on section 2.3.3.1, mediumint would be suggested as NUMBER(7,0) and mediumint does not exists in Oracle. INT gets tricky, as liquibase translate it as INTEGER. Oracle treats INTEGER as NUMBER(38,0) which is like a BIGINT or the maximum size support. Following the same documentation, it's probably best to be used as NUMBER(10,0).
#3292