![]() ![]() However as a well seasoned programmer, I learned decades ago to accept that this is just something you have to live with unless you're fortunate enough to be developing a closed system where you know your pseudo null values will not potentially conflict in this way. I am aware that this will incur a performance hit and would be time consuming to implement. I am aware that to allow NULL values in the memory would require a multitude of pointer checks (within the hidden from us end users code) on almost every date, string, decimal and integer operation. Regarding this potential for pseudo null value clashes with real values, I take it that you're more or less saying that Outsystems would rather pass the buck on for us end users to resolve than fix this fundamental architectural flaw. I am well aware of this limitation in the platform and that (potential pseudo null value clashes aside), the integrations studio setting convert to/from NULL value in Database does not do what it says on the box. How to set timestamp to NULL during an insert to DB or an update (in postgresql). ![]() This probably has a something to do with how these pseudo null values could also be legitimate values in a set of data that Outsystems has no design control over, and maybe the way Outsystems was designed to handle NULL values gives it no real way of distinguishing between the two. However the schoolboy mistake is in not supporting the NULL value native to the 3rd party databases that Outsystems can operate on, but instead in opting to use or continue to use a pseudo null value that Outsystems does not natively translate into real NULL values when inserting or updating them into these 3rd party databases. I do not know if Outsystems once used a closed database system or has always (sort of) supported external databases. This has nothing to do with the debate over whether or not the null pointer is a good, bad or inevitable thing. The inventor of NULL calls it The Billion Dollar mistake. ![]() " It looks like it's a deliberate design decision." I'd call it a schoolboy programming mistake. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |