While debugging an issue, I stumbled upon this. There's no functional downside I suppose, but it was a bit weird. I was trying to find out how it was possible the value of EmailReplica's "ticket ID" was 0 (rather than null).
But apparently: null is allowed, yet 0 is the default? What is the logic behind this (if any, perhaps it's behavior which changed over time)?
Hello Jeffrey,
There is no clear definition of the null value for external fields in the orm. 0 Means null, but sometimes null can also be assigned.... It's a bit of a mess in the DB but the ORM handles it nevertheless.
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
While debugging an issue, I stumbled upon this. There's no functional downside I suppose, but it was a bit weird. I was trying to find out how it was possible the value of EmailReplica's "ticket ID" was 0 (rather than null).
But apparently: null is allowed, yet 0 is the default? What is the logic behind this (if any, perhaps it's behavior which changed over time)?
Hello Jeffrey,
There is no clear definition of the null value for external fields in the orm. 0 Means null, but sometimes null can also be assigned.... It's a bit of a mess in the DB but the ORM handles it nevertheless.