hello
i think i'm having simple serious problem. want transfer huge string (up 3 mb) between custom qpac , workflow context (that other qpac can use string variable).
the length of string variable limited 65535, right? how can transfer such large data strings? ideas?
it great see feedback...
thank you!
nico
i think i'm having simple serious problem. want transfer huge string (up 3 mb) between custom qpac , workflow context (that other qpac can use string variable).
the length of string variable limited 65535, right? how can transfer such large data strings? ideas?
it great see feedback...
thank you!
nico
hi nico
the length of string variable determined underlying data type used store strings in database. limits depend on particular database type you're using. example, believe standard oracle varchar2 limited 2k.
i have 2 suggestions you:
1. use binary varible. implemented in database long raw value, , should unlimited in size. downside many of existing qpacs may not able deal binary variables.
2. use document variable. adobe document variable little string (or binary) on steroids. works binary, has threshold value (default of 64k), on store file in file system rather in database. has significant advantages, including limiting growth of database. has clever caching mechanisms, support clustering, etc. document variable little more difficult deal in custom qpac, not -the com.adobe.idp.document type should self-explanatory. documents good, because tend default type of adobe qpacs use when dealing large amounts of data.
please aware databases (eg mysql) have other limitations, such total number of binary/longvarchar columns can define in 1 table. need experimentation in area well.
i hope helps.
let know you on.
howard
http://www.avoka.com
the length of string variable determined underlying data type used store strings in database. limits depend on particular database type you're using. example, believe standard oracle varchar2 limited 2k.
i have 2 suggestions you:
1. use binary varible. implemented in database long raw value, , should unlimited in size. downside many of existing qpacs may not able deal binary variables.
2. use document variable. adobe document variable little string (or binary) on steroids. works binary, has threshold value (default of 64k), on store file in file system rather in database. has significant advantages, including limiting growth of database. has clever caching mechanisms, support clustering, etc. document variable little more difficult deal in custom qpac, not -the com.adobe.idp.document type should self-explanatory. documents good, because tend default type of adobe qpacs use when dealing large amounts of data.
please aware databases (eg mysql) have other limitations, such total number of binary/longvarchar columns can define in 1 table. need experimentation in area well.
i hope helps.
let know you on.
howard
http://www.avoka.com
More discussions in LiveCycle pre-ES (6.x and 7.x) discussions
adobe
Comments
Post a Comment