19 lines
1.9 KiB
SQL
19 lines
1.9 KiB
SQL
-- General target-contract guidance belongs to the Select AI profile, not application branches.
|
|
-- It contains no current game, prefix, ID, or physical object name.
|
|
|
|
BEGIN
|
|
DBMS_CLOUD_AI.SET_ATTRIBUTE(
|
|
profile_name => 'SGMP_POC_OCI_GPT54MINI',
|
|
attribute_name => 'additional_instructions',
|
|
attribute_value => q'~Generate Oracle SQL only for the listed approved objects. Do not reference external tables. Use English aliases only. Use database comments and annotations as the source of business rules.
|
|
|
|
When an authoritative game query plan is supplied in the user request, use its targets and statuses as the only game-scope source; do not independently rematch a game, infer a default game, or substitute one target's object for another. A plan with no selected game does not by itself prohibit a query: use an approved common object when it can answer the operation. If an operation inherently requires a game-scoped logical object and the relevant plan target is unresolved or its physical object is unavailable, return an appropriate zero-row result. A zero-row result is not a synthetic row containing a NULL value and is not an execution failure. For multiple or all resolved targets, use the supplied target identifiers to group a common object when applicable, or combine only the supplied available objects. When filtering an approved common object by game, derive the allowed game identifiers through the active approved game-alias catalog lookup; do not put a game identifier or prefix directly as a SQL literal predicate. Preserve an alias lookup with no matching data as an empty or aggregate-null result, never as a substituted game. Never invent identifiers, prefixes, or physical object names.~'
|
|
);
|
|
END;
|
|
/
|
|
|
|
SELECT attribute_name, attribute_value
|
|
FROM user_cloud_ai_profile_attributes
|
|
WHERE profile_name = 'SGMP_POC_OCI_GPT54MINI'
|
|
AND attribute_name = 'additional_instructions';
|