A new topic, 'Oracle, VARCHAR2 and portability', has been made on a board you
are watching.
You can see it at
http://liquibase.org/forum/index.php?topic=89.new#new
The text of the topic is shown below:
In Oracle world almost no one use VARCHAR type. VARCHAR2 is used instead.
So common Oracle equivalent for Java String type is VARCHAR2, not VARCHAR.
But there is problem, how to write portable change logs - what type should be
used?
We can use VARCHAR2 and it will work fine on Oracle, but will fail on other
databases.
We can use VARCHAR and it will pass OK on all databases, but we don't want it
on Oracle.
Of course we can write double changes: one for Oracle, one for other and use
preconditions - but it's error prone.
So it would be better if liquibase did automatic translation from VARCHAR to
VARCHAR2. Or maybe even better would be if one can specify type "String(40)"
and liquibase translated it (depending on database) to VARCHAR(40) or
VARCHAR2(40).
And "String(10000)" should be translated to CLOB.
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.
------------------------------------------------------------------------------
_______________________________________________
Liquibase-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/liquibase-user
