Re:Farewell Pandas, and thanks for all the fish
by emmelaich on Thursday August 29, 2024 @04:40PM
(#41395044)
In Oracle, "" is converted to NULL so maybe that's where they get that from.
Re:Farewell Pandas, and thanks for all the fish
by rbanffy on Thursday August 29, 2024 @05:10PM
(#41395328)
You can almost count on Oracle doing the wrong thing…
It never ceases to amaze me they got themselves into a position where they had to introduce a VARCHAR2 type.
Re:Farewell Pandas, and thanks for all the fish
by kstrauser on Thursday August 29, 2024 @04:47PM
(#41395093)
Whoa, you're right.[0] I wouldn't have expected that at all.
[0] https://docs.oracle.com/en/database/oracle/oracle-database/1...
In that case, `select * from users where middle_name is null` gives us a set of users to prod for missing information next time we talk to them. `...where middle_name = ''` gives us a list of people without a middle name, should we care.
Edit:
A related aside is that Django's ORM's handling of NULL gives me freaking hives. From https://docs.djangoproject.com/en/5.1/ref/models/fields/#nul...:
> If a string-based field has null=True, that means it has two possible values for “no data”: NULL, and the empty string. In most cases, it’s redundant to have two possible values for “no data;” the Django convention is to use the empty string, not NULL.
I've been around numerous Django devs when they found out that other DBs and ORMs do not remotely consider NULL and empty string to be the same thing.