This content has been marked as final. Show 5 replies
The limitation isn't really a limitation on the application server side. It's a limitation in PL/SQL - the varchar2 data type in PL/SQL can only contain 32767 bytes. (in the database, the limit is even smaller - 4000 bytes) In some situations, you can get around this by using CLOB or BLOB instead of VARCHAR2. But don't try that on an Oracle 8 or earlier database, and it may be limited in Oracle 9 - later versions have improved the compatibility of LOB types with VARCHAR2.
Is it APEX limitation ? Database column type is CLOB and field on the form defined as Rich Text Editor field. I don't use my own PL/SQL procedure but standard APEX form with source for field defined as Database Column. Is there any workaround ?
that's an APEX limitation, as wwv_flow.accept always handles your page items as varchar2(32767).
I don't know any solution for this problem in APEX. The only "workaround" that comes to my mind would be to create a servlet that supports larger objects and integrate it in your page via iframe.
to submit them as separate AJAX requests.
Edited by: le on Oct 27, 2010 4:39 PM
That's an example how it could be done:
1) Create several hidden items,
3) Clear original item with big value
4) in after submit process concatenate values of hidden items.
I think this solution is from category "quick and dirty" solutions.