[ 
https://jira.nuxeo.org/browse/NXP-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59040#action_59040
 ] 

Florent Guillaume edited comment on NXP-3993 at 3/26/10 3:02 PM:
-----------------------------------------------------------------

Now, (together with NXP-3995 changes), string fields are by default some kind 
of VARCHAR column (depending on the database).
This makes them comparable and orderable, but size-limited in some databases.

To have a string field use a CLOB-like column, you have to specify it in the 
repository configuration, by giving it a "largetext" type, for instance:
  <schema>
    <field type="largetext">note</field>
  </schema>

If the database already exists, VCS will use whatever exists in the database 
for the column type (VARCHAR or CLOB), which makes backward-compatibility 
possible.


      was (Author: fguillaume):
    Now, (together with NXP-3995 changes), string fields are by default some 
kind of VARCHAR column (depending on the database).
This makes them comparable and orderable, but size-limited in some databases.

To have a string field use a CLOB-like column, you have to specify it in the 
repository configuration, by giving it a "largetext" type, for instance:
  <schema>
    <field type="largetext">note:note</field>
  </schema>

If the database already exists, VCS will use whatever exists in the database 
for the column type (VARCHAR or CLOB), which makes backward-compatibility 
possible.

  
>  Avoid 2000 characters limit for some fields
> --------------------------------------------
>
>                 Key: NXP-3993
>                 URL: https://jira.nuxeo.org/browse/NXP-3993
>             Project: Nuxeo Enterprise Platform
>          Issue Type: Bug
>          Components: Core SQL Storage
>    Affects Versions: 5.2 GA
>            Reporter: Delphine Renevey
>            Assignee: Florent Guillaume
>            Priority: Blocker
>             Fix For: 5.3 RC
>
>
> In some cases the Oracle server fails to set values for some textual fields 
> because the value uploaded is too large. The DB text columns are set to 
> NCHARVAR2(2000), value apparently exceeded by the fields values. The limit of 
> 2000 is intrinsic to Oracle NVARCHAR2, beyond that a NCLOB must be used.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets

Reply via email to