Some basic datatypes and functions in oracle compatibility mode do not work
(MDEV-19162)
|
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Data Manipulation - Insert |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | Technical task | Priority: | Major |
| Reporter: | Faisal Saeed (Inactive) | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | Compatibility | ||
| Description |
|
A lot of customers ask for the ability for LOAD DATA INFILE to work similarly to Oracle's SQLLOADER which has the ability to specify a "BAD" file as one of the parameters. All the rejected records from the database are written to the "BAD" file so that the team can review those records and identify the root cause. Currently, there is no way to find out what went on and which records out of millions failed. This is required for Oracle Migration projects. |
| Comments |
| Comment by Daniel Black [ 2020-02-17 ] |
|
Rather than a file do you think a table with structure `lineno BIGINT UNSIGNED NOT NULL PRIMARY KEY, line TEXT, error enum|text |
| Comment by Daniel Black [ 2020-09-07 ] |
|
duplicate of MDEV-13046 |
[MDEV-20027] 
` would be acceptable? This avoid client protocol extensions needed to support "LOCALINFILE" "files" or server side files.