Doctrine considers empty string as null (I mean Oracle)
We are on the last stretch of our project and we need to deliver soon.
Sometimes, we have to make concessions and compromises in order to make sure to deliver in time.
We wanted to use a column that could have 3 different significations.
The possible values we wanted were:
The problem was that when using Doctrine to insert/update the field when using an empty string, it would insert/update a null instead.
We first thought the problem was Doctrine but we later found out the problem was Oracle.
Maybe I am too used to MySQL but this seems like a WTF to me.
So we cannot do our dirty hack. Using empty string and null to mean something different is not kosher.
I realized that this oracle "feature" have a consequence. If we were using MySQL than it would mean that an empty string would also be considered null (for compatibility reasons).
Make a Payment to Christian Roy