You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need a way for the external APIs (like Java) to be able to check if it is compatible, when calling utPLSQL, so that the calling (Java) API can first check if the version that it is depending on is compatible with current version.
That could be done by providing a compatibility check. ut_run.check_compatibility_with_version( a_version varchar2)
The function would return true/false depending on the result of check.
The check would execute the following pseudo-code:
begin
l_result := false;
l_version = current_version number (major.minor.bugfix);
if a_version.major = l_version.major
and (a_version.minor = l_version.minor
or a_version.minor = l_version.minor and a_version.bugfix <= l_version.bugfix) then
l_result := true;
end if;
return l_result;
end if;
So versions are compatible:
if major is equal and framework minor >= requested
if major is equal and minor is equal and framework bugfix >= requested
The text was updated successfully, but these errors were encountered:
I'm not sure that the approach from dbms_db_version would work well, as we will have more versions and adding a constant for each version seems not right.
A rule-based check would be nice.
We could have constants/functions for version parts:
gc_major
gc_minor
gc_bugfix
gc_build
So that the calling side can either use rule-based version compatibility check or use the version parts individually.
We need a way for the external APIs (like Java) to be able to check if it is compatible, when calling utPLSQL, so that the calling (Java) API can first check if the version that it is depending on is compatible with current version.
That could be done by providing a compatibility check.
ut_run.check_compatibility_with_version( a_version varchar2)
The function would return true/false depending on the result of check.
The check would execute the following pseudo-code:
So versions are compatible:
The text was updated successfully, but these errors were encountered: