Discussions
Categories
- 196.7K All Categories
- 2.2K Data
- 235 Big Data Appliance
- 1.9K Data Science
- 449.9K Databases
- 221.6K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 549 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 532 SQLcl
- 4K SQL Developer Data Modeler
- 186.9K SQL & PL/SQL
- 21.3K SQL Developer
- 295.4K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.1K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 153 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 158 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 203 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 400 LiveLabs
- 37 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.6K Other Languages
- 2.3K Chinese
- 170 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 230 Portuguese
SQLcl apex export split problem
Hi!
If your application page number has more than 5 digit then "-split" option produce not page_NNNNN.sql file, but page_NNNNN_XXX.sql where XXX just some ORDER BY suffix. Therefore, the same page may be sliced to different result files (comparing to previous run).
For example:
1) You have only pages 100001 and 100005. Result: page_10000_001.sql for page 100001, page_10000_002.sql for page 100005 (for example, I don't remeber exact file names);
2) You have added page 100002. Result: page_10000_001.sql for 100001, page_10000_002.sql for page 100002 and page_10000_003.sql for page 100005.
This "feature" ruins possibility of correct APEX-Git (and any other versioning system) binding. Is there a way for "-slice" option to always save APEX page into .sql file with static name (based only on page number)?
Comments
-
This code was written a very long time ago. It seems that the goal was for page exports to be sorted in numerical order on the file system. It also seems that the original developer did not expect page numbers to be greater than 100,000. The page numbers could be padded with additional zeros, but that would negatively impact those that are currently storing pages in the file system. Not to mention, having additional zeros will make things more difficult to read.
Because the large page numbers seem to be the exception, I am proposing to keep the page format as is for pages below 100,000 and simply format page numbers without padding for greater than 100,000.
For example, Page 100005 would be exported as page_100005.sql, Page 234000005 would be exported as page_234000005.sql.
Let me know if you have concerns or other suggestions.
-
Seems as good solution. Thank you.
-
Hi,
Do you know if this fix will make it into an upcoming version of SQLcl?
Right now, I'm on 21.4 and this bug is still present in that version.
-
-
SQLcl uses the internal APEX packages for exporting the pages. The bug has been fixed in APEX version 22.1 which has not been released yet (coming soon).
-
That's good news!
My thanks to you and to the APEX team.
-
Indeed!
Thank you!