Oracle TypeMap must allow up to 4000 characters in VARCHAR2 / NVARCHAR2 fields #612
Comments
jonnybee
pushed a commit
to jonnybee/fluentmigrator
that referenced
this issue
Jun 4, 2015
tommarien
added a commit
that referenced
this issue
Jun 20, 2015
Updated Raw datatype map and unit tests. RAW(MAX) is not a valid datatype Added unit tests for OracleTypeMap #612 Update Oracle TypeMap
|
Closed by #613 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
see: http://docs.oracle.com/cd/B28359_01/server.111/b28318/datatype.htm#CNCPT1822
The VARCHAR2 datatype stores variable-length character strings. When you create a table with a VARCHAR2 column, you specify a maximum string length (in bytes or characters) between 1 and 4000 bytes for the VARCHAR2 column
FluentMigrator has a limit of 2000 characters and if above will create a CLOB column. The limit should be altered to allow up to 4000 characters.
The same goes for NVARCHAR2 fields.
The maximum length of an NVARCHAR2 column is 4000 bytes. It can hold up to 4000 characters. The actual data is subject to the maximum byte limit of 4000.
I can submit PR if you will accept!
The text was updated successfully, but these errors were encountered: