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
Copy file name to clipboardExpand all lines: EN/modules/ROOT/pages/v3.0/1.adoc
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,15 +3,15 @@
3
3
:sectnumlevels: 5
4
4
5
5
6
-
== Version Inroduction
6
+
== Version Introduction
7
7
8
8
[**Release date: November 17, 2023**]
9
9
10
-
IvorySQL 3.0 is based on PostgreSQL 16.0 includes various fixes from PostgreSQL 16.0, for more detailed updates and bug fixes in PostgreSQL 16.0, see the official https://www.postgresql.org/docs/release/16/[PostgreSQL 16.0 Release Notes].
10
+
IvorySQL 3.0 is based on PostgreSQL 16.0 and includes various fixes from PostgreSQL 16.0, for more detailed updates and bug fixes in PostgreSQL 16.0, see the official https://www.postgresql.org/docs/release/16/[PostgreSQL 16.0 Release Notes].
11
11
12
12
== Updates on Version 3.0 vs 2.3
13
13
14
-
IvorySQL 3.0 represents a significant architectural evolution, marking a departure from the usage patterns of version 2.3. It's important to note that some functionalities available in 2.3 are not yet supported in the new version. Here's a breakdown of the key feature differences between these two versions:
14
+
IvorySQL 3.0 signifies a major shift in its architectural design, diverging from the operational patterns established in version 2.3. It's crucial to recognize that certain features present in version 2.3 have not been incorporated into the new version. The following is an overview highlighting the primary distinctions in features between these two iterations:
@@ -81,7 +81,7 @@ IvorySQL 3.0 represents a significant architectural evolution, marking a departu
81
81
|Procedure|Syntax compatibility is supported, and the OUT parameter is supported|support|support
82
82
|Anonymous block|Syntax compatibility is supported, and the OUT parameter is supported|not support|support
83
83
|Nested subroutines|Nested stored procedures, functions, and so on are supported|not support|support
84
-
|Merge|The Merge function of PG and the Merge function compatible with Oralce syntax are supported|not support|support
84
+
|Merge|The Merge function of PG and the Merge function compatible with Oracle syntax are supported|not support|support
85
85
|q`|Compatible escapes are supported|support|support
86
86
|Keyword processing|Supports the processing of keywords in the database|not support|support
87
87
.4+|Object case conversion|All uppercase plus double quotation marks are converted to lowercase|not support|support
@@ -117,9 +117,9 @@ IvorySQL 3.0 represents a significant architectural evolution, marking a departu
117
117
118
118
== Enhancements
119
119
120
-
=== ivorysql frame
120
+
=== IvorySQL core framework
121
121
122
-
* Add double Parser to support different database parsers https://github.com/IvorySQL/IvorySQL/issues/208[Problem details]
122
+
* Add dual parser functionality to support different database parsers https://github.com/IvorySQL/IvorySQL/issues/208[Problem details]
123
123
* Added dual ports to support different database port numbers https://github.com/IvorySQL/IvorySQL/issues/200[Problem details]
124
124
* Add initdb -m to support postgres mode or oracle mode https://github.com/IvorySQL/IvorySQL/issues/212[Problem details]
125
125
@@ -136,7 +136,7 @@ IvorySQL 3.0 represents a significant architectural evolution, marking a departu
136
136
* Creating a function or procedure in SQL parser supports nested subprocedures https://github.com/IvorySQL/IvorySQL/issues/312[Problem details]
137
137
* Nested child processes and functions IS/As do not need to be declared https://github.com/IvorySQL/IvorySQL/issues/303[Problem details]
138
138
139
-
=== Other
139
+
=== Others
140
140
* Add meson compilation to action https://github.com/IvorySQL/IvorySQL/issues/512[Problem details]
141
141
* Support for meson compilation https://github.com/IvorySQL/IvorySQL/issues/325[Problem details]
142
142
* Add compatible test cases https://github.com/IvorySQL/IvorySQL/issues/479[Problem details]
@@ -148,7 +148,7 @@ IvorySQL 3.0 represents a significant architectural evolution, marking a departu
148
148
* Compatible with Oracle built-in data types and built-in functions https://github.com/IvorySQL/IvorySQL/issues/239[Problem details]
149
149
* Add the plisql extension https://github.com/IvorySQL/IvorySQL/issues/211[Problem details]
150
150
151
-
> Description:For more information about the new features, please refer to the feature list in this document center
151
+
> Description:For more information about the new features, please refer to the feature list in this document center
152
152
153
153
== Fixed issue
154
154
@@ -163,7 +163,7 @@ IvorySQL 3.0 represents a significant architectural evolution, marking a departu
163
163
* Solve the problem that the NLS parameter is set to 12-hour clock, and the default rule for completing AM/PM keywords is inconsistent with Oracle https://github.com/IvorySQL/IvorySQL/issues/405[Problem details]
164
164
* The DEFAULTED field value in the function/stored procedure xx_arguments view created with default values is an issue of N https://github.com/IvorySQL/IvorySQL/issues/379[Problem details]
165
165
* Functions/stored procedures without permissions can be viewed in all_procedures/all_arguments/all_source views https://github.com/IvorySQL/IvorySQL/issues/378[Problem details]
166
-
* When the self-incrementing column type is numer type and the precision is specified, when a null value is inserted by default on null, it is not the inserted concrete sequence value, but the inserted null value https://github.com/IvorySQL/IvorySQL/issues/386[Problem details]
166
+
* When the self-incrementing column type is number type and the precision is specified, when a null value is inserted by default on null, it is not the inserted concrete sequence value, but the inserted null value https://github.com/IvorySQL/IvorySQL/issues/386[Problem details]
0 commit comments