![]() It seems to be implemented not as a real table. To get more info why MariaDB behaves like this I tried to investigate a bit more: We opened a bug at MariaDB without much hope that this bug will be fixed soon. The first query should work as well but does not. Mariadb> SELECT 'Hello World!' FROM dual :-( But this query on the dual table seems to work: Mariadb> SELECT PIPES_AS_CONCAT,ANSI_QUOTES,IGNORE_SPACE,ORACLE,NO_KEY_OPTIONS,NO_TABLE_OPTIONS,NO_FIELD_OPTIONS,NO_AUTO_CREATE_USER,SIMULTANEOUS_ASSIGNMENT |įirst of all I tried the function of the basic and fundamental table in Oracle, the DUAL table: To verify if the sql_mode is already set you can use the following statement: Or you can make this setting persistent in your my.cnf MariaDB configuration file: The activation of the modification of the MariaDB PL/SQL parser is achieved by changing the sql_mode as follows: ![]() So the old MariaDB parser would through some errors without modification. Oracle PL/SQL syntax is quite different from old MySQL/MariaDB SQL/PSM syntax. One of the features which interests me most is the MariaDB Oracle PL/SQL compatibility mode. MariaDB 10.3 was released GA a few weeks ago.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |