A new topic, '[LB1.9.3] Internal datatype conversion to target databases', has
been made on a board you are watching.
You can see it at
http://liquibase.org/forum/index.php?topic=51.new#new
The text of the topic is shown below:
Trying LiquiBase for the first time I think this tool can help me upgrading my
databases. Planning this for both MySQL and Oracle with the same changelog I
found some data type conversion issues. For some types the the internal
LiquiBase is not converted to the correct target database type or a possibly
better fit is available. The table below lists the internal LiquiBase types as
well as the target database types for Oracle and MySQL. Another column is added
with the requested data type.
LiquiBase typeOracleRequestedMySQLRequestedDOUBLEDOUBLENUMBER or
FLOATDOUBLELONGVARCHARCLOBTEXTLONG TEXTTINYINTTINYINTNUMBER(3)
?TINYINTVARCHARVARCHARVARCHAR2VARCHAR
The double and tinyint are the most curious, Oracle doesn't event accept these
as datatype and can be considered a bug. The VARCHAR is now automatically
converted to varchar2 but possibly Liquibase can do this.
For MySQL the LONGVARCHAR, can this be set to LONG TEXT? The Liquibase type
TEXT gives support for normal length TEXT fields, then the LONGVARCHAR can
support LONG TEXT, or should a additional type be added to the Liquibase for
long text fields in MySQL?
Regards,
Chris
Unsubscribe to new topics from this board by clicking here:
http://liquibase.org/forum/index.php?action=notifyboard;board=1.0
Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Liquibase-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/liquibase-user
