PL/SQL parser - Phase 2
(MDEV-10764)
|
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | OTHER |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Technical task | Priority: | Major |
| Reporter: | Alexander Barkov | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 2 |
| Labels: | Compatibility, Oracle | ||
| Issue Links: |
|
||||||||||||
| Description |
| Comments |
| Comment by Michael Widenius [ 2016-08-18 ] |
|
Note that this is true for VARCHAR columns only. For CHAR columns "" is not same as NULL. The main challenge to do this is that we can't change the storage format as the data must be accessible in both oracle mode and ansi sql mode. This functionality is quite hard to do, especially for indexed columns, so I recommend that we don't implement this if not critically necessary. This comes from that we would have to change all queries that compare varchar strings from Copying code also gets complicated as it's not clear if should store "" or null in the receiving table We would also have to convert all varchar string results from "" to NULL when sending to client. From Oracle's documentation: "Oracle Database currently treats a character value with a length of zero as null. However, this may not continue to be true in future releases, and Oracle recommends that you do not treat empty strings the same as nulls" |
| Comment by Alvin Richards (Inactive) [ 2016-10-17 ] |
|
We are considering to implement both of the following options (with a switch) Transform Insert Transform Select
|
| Comment by Jérôme Brauge [ 2016-12-07 ] |
|
Hi, Example 2: COALESCE We are looking forward to some features being implemented (like Best regards. |