The SQL execution generated by the export Oracle table data function will report an error #15929
Replies: 4 comments 2 replies
-
@bianyun1981 |
Beta Was this translation helpful? Give feedback.
-
@uslss Although modifying the value of this configuration can temporarily solve this problem, there seems to be a little inconvenient to use, that is: if I am used to setting this to a value greater than 1 under the MySQL connection (ie: a single statement inserts multiple rows ), then when I switch back and forth between MySQL and Oracle, when exporting data, I have to change the value of this configuration every time. I feel that whether this configuration takes effect should be pre-judged with the type of connection. For example, Oracle does not support the syntax of inserting multiple rows of data in a single statement, so the value of this configuration should be fixed at 1, and it is not allowed to be modified. |
Beta Was this translation helpful? Give feedback.
-
Hello @bianyun1981 We have a special setting for the multiple exports for the Oracle database: It will return something like this: INSERT ALL
INTO public.newtable (column1,column2,column3) VALUES ('dogThe','dogThe quick brown fox jumps over the lazy',300393)
INTO public.newtable (column1,column2,column3) VALUES ('the la','bro',129497)
INTO public.newtable (column1,column2,column3) VALUES ('fox jumps over th','the lazy dogThe quick brown f',332652)
SELECT 1 FROM DUAL; Thanks for the idea, but DBeaver usually tries to save your preferences/settings. If we will change export settings depending on the Database - it can be confusing. |
Beta Was this translation helpful? Give feedback.
-
Thank you for your reply. I didn't know that Oracle supports this form of syntax for inserting multiple rows with a single statement, so this configuration (Data rows per statement) makes sense for Oracle. As for the fact that DBeaver saves preferences for different export settings based on different database types can be confusing, I agree that it is. However, if a configuration (such as a configuration in export table data: "Upsert keyword") needs to be set to different values for different types of databases, then the saving of preferences for this configuration should not be saved globally. Even if this configuration value is not saved by database type, it should at least save one configuration value per connection, so that each connection only needs to set this configuration once. Otherwise, when switching between different types of databases, you may need to modify this configuration every time you switch. |
Beta Was this translation helpful? Give feedback.
-
System information:
Connection specification:
Describe the problem you're observing:
When I used DBeaver to export Oracle table data, I found that the generated SQL statement used the feature of inserting multiple rows in a single statement that Oracle does not support. An example of the generated SQL statement is as follows:
Beta Was this translation helpful? Give feedback.
All reactions