Thanks for the new version!
One small feature that would make the plugin even better: a dedicated TriggeringElement attribute.
Currently, we have to set it manually in PL/SQL, like:
apex_application.g_x01 := '#MY_BUTTON_ID';
It works — but isn’t very intuitive or user-friendly.
Thanks for the new version!
One small feature that would make the plugin even better: a dedicated TriggeringElement attribute.
Currently, we have to set it manually in PL/SQL, like:
apex_application.g_x01 := '#MY_BUTTON_ID';
It works — but isn’t very intuitive or user-friendly.
But what happen if the tool functions returns are very large amount of data (Thousands of records in tt_users) ?
I imagine that each AI model have a limited context size.
But what happen if the tool functions returns are very large amount of data (Thousands of records in tt_users) ?
I imagine that each AI model have a limited context size.
If your cursor is below the SET DEFINE OFF; line in a .sql file, it still triggers the prompt. You have to place the cursor above it to run the file.
If your cursor is below the SET DEFINE OFF; line in a .sql file, it still triggers the prompt. You have to place the cursor above it to run the file.