tag:blogger.com,1999:blog-741750605858169835.post546534319884937921..comments2024-01-24T14:53:02.919+00:00Comments on Stephen Colebourne's blog: Oracle RDBMS empty string and nullStephen Colebournehttp://www.blogger.com/profile/01454237967846880639noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-741750605858169835.post-30813485248189731142017-07-07T09:09:54.950+01:002017-07-07T09:09:54.950+01:00Hello,
And what about the possibility to do that ...Hello,<br /><br />And what about the possibility to do that in stored procedure ?<br /><br />JulienAnonymoushttps://www.blogger.com/profile/06294657467893447841noreply@blogger.comtag:blogger.com,1999:blog-741750605858169835.post-13368773831593297252014-09-08T12:31:54.480+01:002014-09-08T12:31:54.480+01:00Yep, that's one of the more "awesome"...Yep, that's one of the more "awesome" feature sof Oracle database.<br /><br />The big caveat is not the fact that the two things are the same, which can be justified depending on philosophy, the big caveat is that you must be careful not to have empty strings in situations where SQL's three valued logic will bite you (and wouldn't bite you in other databases). One such example is that the following always yields UNKNOWN:<br /><br />'X' NOT IN ('A', 'B', '')<br /><br /><a href="http://blog.jooq.org/2012/01/27/sql-incompatibilities-not-in-and-null-values" rel="nofollow">More info here</a>Lukas Ederhttps://www.blogger.com/profile/02028559621679932902noreply@blogger.com