Hi Jeff! I have been watching your videos and reading your posts about ORDS and using it to create REST APIs for an Oracle database. I have noticed that while the builtin version of Liquibase that ships with SQLcl has special support for APEX applications I could not find anything in the way of support for REST APIs. How are we supposed to use SQLcl and Liquibase to version control our REST APIs? Thanks in advance for any answer. Regards Sevre
See the help avail for the LB (liquibase) command. usage: lb genobject -type {ORDS} -name NAME [-noenable] [-noprivs] [-context CONTEXT] [-label LABEL] [-fail] [-replace] [-runonchange] [-runalways] [-debug] Generate change log for an ORDS module named arguments: -type {ORDS} Generate output for ORDS Module -name NAME Module name -noenable Dictates whether the enable_schema call will be included in the export (default: true) -noprivs Dictates whether Privs will be included in the export. (default: true) So if I have a module named 101 (and I do), I can create a changeLog for it using this command SQL> lb genobject -type ORDS -name 101 Action successfully completed please review created file ords-rest_101.xml SQL> !head -n10 ords-rest_101.xml
Great information
thanks so much!
you are very welcome! thanks for taking the time to leave a comment!
Hi Jeff!
I have been watching your videos and reading your posts about ORDS and using it to create REST APIs for an Oracle database. I have noticed that while the builtin version of Liquibase that ships with SQLcl has special support for APEX applications I could not find anything in the way of support for REST APIs. How are we supposed to use SQLcl and Liquibase to version control our REST APIs?
Thanks in advance for any answer.
Regards Sevre
See the help avail for the LB (liquibase) command.
usage: lb genobject -type {ORDS} -name NAME [-noenable] [-noprivs]
[-context CONTEXT] [-label LABEL] [-fail] [-replace]
[-runonchange] [-runalways] [-debug]
Generate change log for an ORDS module
named arguments:
-type {ORDS} Generate output for ORDS Module
-name NAME Module name
-noenable Dictates whether the enable_schema call will be
included in the export (default: true)
-noprivs Dictates whether Privs will be included in the export.
(default: true)
So if I have a module named 101 (and I do), I can create a changeLog for it using this command
SQL> lb genobject -type ORDS -name 101
Action successfully completed please review created file ords-rest_101.xml
SQL> !head -n10 ords-rest_101.xml
!head -n25 ords-rest_101.xml
TRUE,
p_schema => 'ADMIN',
p_url_mapping_type => 'BASE_PATH',
p_url_mapping_pattern => 'admin',
p_auto_rest_auth => FALSE);
ORDS.DEFINE_MODULE(
p_module_name => '101',
p_base_path => '/101/',...
@@JeffSmiththat thank you for your answer, can’t believe I missed that in the documentation..
@@fjakk1 no worries, I'm on a constant mission to improve the docs of it means only helping one more user