{"id":3327,"date":"2024-03-25T10:20:00","date_gmt":"2024-03-25T10:20:00","guid":{"rendered":"https:\/\/www.bohort.nl\/?p=3327"},"modified":"2024-05-23T11:50:39","modified_gmt":"2024-05-23T11:50:39","slug":"using-oracle-select-ai-in-an-apex-application","status":"publish","type":"post","link":"https:\/\/www.bohort.nl\/en\/2024\/03\/25\/using-oracle-select-ai-in-an-apex-application\/","title":{"rendered":"Using Oracle Select AI in an (APEX) Application"},"content":{"rendered":"

This is a follow-up post on Oracle Select AI. In my previous post <\/a>I explained how to setup Oracle Select AI, and how that enables you to chat with your database. In this post I will take it one step further and show you how Select AI can be used in an application. I can be an application built in any technology. Read along and benefit from the below.<\/p>\n\n\n\n

The Secret is Simple<\/h3>\n\n\n\n

As you cannot use Select AI itself from within an application, Oracle added the “GENERATE” function to the DBMS_CLOUD_AI package. This function provides AI translation in a stateless manner. With your existing AI profile, you can use this function to perform the supported actions such as showsql, narrate, or chat. The default action is showsql.<\/p>\n\n\n\n

<\/circle><\/circle><\/circle><\/g><\/svg><\/span><\/path><\/path><\/svg><\/span>
DBMS_CLOUD_AI<\/span>.<\/span>GENERATE<\/span>(<\/span><\/span>\n                    <\/span>prompt<\/span> <\/span>=><\/span> <\/span>'what is the total number of customers\u2019,<\/span> <\/span><\/span>\n                    <\/span>profile_name<\/span> <\/span>=><\/span> <\/span>'openai_gpt35\u2019,<\/span> <\/span><\/span>\n                    <\/span>action<\/span> <\/span>=><\/span> <\/span>'showsql'<\/span>)<\/span><\/span>\n<\/span><\/code><\/pre><\/div>\n\n\n\n
The “GENERATE” function does NOT<\/strong> support the runsql<\/code>\u00a0action. If you supply the\u00a0runsql<\/code>\u00a0action, it returns the following error: <\/p>\n\n\n\n
ORA-20000: runsql action is not supported by generate function ORA-06512: at \"C##CLOUD$SERVICE.DBMS_CLOUD\", line xxxx 
ORA-06512: at \"C##CLOUD$SERVICE.DBMS_CLOUD_AI\", line 2696 ORA-06512: at line x<\/pre>\n\n\n\n
The reason for this is that allowing arbitrary SQL execution within an AI generation context could pose security risks. With the GENERATE function you will get the SQL Statement that you need, however there is some work to be done in order to actually run the statement in your application.<\/p>\n\n\n\n
So what are your Options?<\/h3>\n\n\n\n
In order to run the SQL that was returned by the “GENERATE” function there are several options. In this post I will provide (in my opinion) the easiest. This is to use a Classic APEX Report, which is based on a Function that returns a SQL Statement. It works almost instant, after you provide the PROMPT that can be entered by the user. <\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
And that is really it. Nothing complex. What is debatable is the format which you show the query result to the user. Maybe you don’t want a table, maybe a diagram or a form makes more sense, but that is something for another post.<\/p>","protected":false},"excerpt":{"rendered":"
This is a follow-up post on Oracle Select AI. In my previous post I explained how to setup Oracle Select AI, and how that enables you to chat with your…<\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_kadence_starter_templates_imported_post":false,"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","footnotes":""},"categories":[91,93,73,1],"tags":[],"class_list":["post-3327","post","type-post","status-publish","format-standard","hentry","category-ai","category-apex","category-apex-world","category-niet-gecategoriseerd"],"_links":{"self":[{"href":"https:\/\/www.bohort.nl\/en\/wp-json\/wp\/v2\/posts\/3327","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.bohort.nl\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.bohort.nl\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.bohort.nl\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bohort.nl\/en\/wp-json\/wp\/v2\/comments?post=3327"}],"version-history":[{"count":2,"href":"https:\/\/www.bohort.nl\/en\/wp-json\/wp\/v2\/posts\/3327\/revisions"}],"predecessor-version":[{"id":3330,"href":"https:\/\/www.bohort.nl\/en\/wp-json\/wp\/v2\/posts\/3327\/revisions\/3330"}],"wp:attachment":[{"href":"https:\/\/www.bohort.nl\/en\/wp-json\/wp\/v2\/media?parent=3327"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.bohort.nl\/en\/wp-json\/wp\/v2\/categories?post=3327"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.bohort.nl\/en\/wp-json\/wp\/v2\/tags?post=3327"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}