Skip to Main Content
Feature Request FR-2536
Product Area APIs
Status DELIVERED

34 Voters

Increase Varchar2 column limit for APEX_DATA_PARSER to 32K

prerna.p.sinha Internal · May 23 2022

Idea Summary
For APEX_DATA_PARSER , VARCHAR2 columns are limited to 4,000 byte, regardless of the MAX_STRING_SIZE database parameter. That means, that APEX_DATA_PARSER uses the CLOB data type as soon as the content is larger than 4,000 bytes.

So, The environment where MAX_STRING_SIZE is 32,000 bytes, APEX_DATA_PARSER still treats values greater than 4000 bytes as CLOB

Use Case
While loading a CSV file in  32K compatible apps i.e.VARCHAR2 has limit of 32K bytes, APEX_DATA_PARSER  treats text values greater 4K and less than 32K as CLOB .

This has been delivered in Oracle APEX 22.2 as part of bug 34230448!

Comments

Comments

  • jayson hanes Admin OP 3.1 years ago

    This could be achieved, but it would be good to see if there is more demand for this. It's not a trivial amount of work to make this enhancement part of the product.

  • zolo OP 3.1 years ago

    Not a critical issue. The table needs a trigger that performs clob varchar2 conversion and stores varchar2, but can be useful in the long run.

  • abhinav.verma OP 3.1 years ago

    Hi There, 

    I see this ticket needs more support. Is there a defined count of number of votes/support needed for any enhancement to be considered for future release ?

  • fac586 OP 3.1 years ago

    Someone is going to have to explain why this is so all-fired important to Oracle employees.

    It's not something that I would lose a minute's sleep about…

  • carsten.czarski APEX Team OP 3.1 years ago

    @prerna.p.sinha Can you please elaborate a bit about where and how the current 4K limit is blocking you?

    As you  might have seen, APEX_DATA_PARSER treats larger values as CLOB, and CLOBs can still loaded into the 32K VARCHAR2 columns (as long as the CLOB Content is below 32K of course). APEX_DATA_PARSER supports up to 20 CLOB columns.

    Do you have to process more than 20 columns with contents larger than 4K in your uploads?

  • prerna.p.sinha OP 3.1 years ago

    We are working for an application where we are using VARCHAR2 type columns for loading the data using APEX DATA PARSER. In case of large data we will have to implement a custom logic to check its length and process it further.  So, it will be good if the APEX DATA PARSER itself increases its limit for VARHCAR2 to 32K in 32k compatible environment, we will then use the native code only.