StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POAPEX: Export *only* app components programmatically - how?
text
Body
copied!<p>At a higher level I have a task to maintain my APEX application in a Subversion repository, thus, I need to implement a consistent (and easily importable) set of files.</p> <p>My first option was to user Oracle's Java-based utilities (APEXExport & Apexsplitter). </p> <p>Export worked just fine, but I didn't want to keep large app-wise files, and splitter part appeared to be error-prone (I wasn't able to re-import splitted application due to some constraint violations, which I didn't investigate).</p> <p>Another option, I tried to use WWV_FLOW_UTILITY's API. This one is fine for both app-wise and page-wise export, which I currently have, but I would also like to keep application components as separate files.</p> <p>I don't actually want to export anything using APEX web interface; I've done some additional research upon system packages and found WWV_FLOW_GEN_API2, which seems to be able to export components separately, but it seems unintuitive (at least in comparison with WWV_FLOW_UTILITY) and undocumented.</p> <p>So... Any chance for an easy way to export components into separate files, or my only way here is to try to play with gen_api2 or (lol, actually, no) try to emulate web interface and reproduce these HTTP POST requests that generate an .sql for any given set of components?</p> <p>Thanks.</p> <p><strong>update</strong>: Here's the error I get when I try to import splitted app:</p> <pre><code>......Button Template 572358005406745047 begin * ERROR at line 1: ORA-00001: unique constraint (APEX_040100.WWV_FLOW_BUTTON_TEMP_PK) violated ORA-06512: at "APEX_040100.WWV_FLOW_API", line 6711 ORA-06512: at line 3 </code></pre>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload