title: How to handle versioning with Oracle Apex
body: <p>Oracle Apex is great. The biggest problem I have with it is using it along with source code control. Generally after making a change, the entire application gets exported and the resulting SQL script checked into source code control. </p>
  
  <p>The problem is that because it's unclear what most of that exported script is doing, I have to treat is as essentially a binary file. That means changes from multiple source code branches can't be merged together, which severely limits its usefulness.</p>
  
  <p>I've heard of some people exporting each page and putting those into source code control individually. First, that sounds like a major pain. Second, Apex does not allow you to import a page into any application other than the one from which it was exported. So it's hard to have two developers working in their own copy of an application at once.</p>
  
  <p>Has anyone found a good way to handle Apex with source code control? I'm using Subversion, thought I doubt it makes a difference.</p>