Original DBF/CDX tables doesn't handle with null values.
So, when I have started to changed data with SQL sources, my application didn't know how to handle those NIL values instead of empty string like it was when the data source was real DBF table.
There were two solutions:
To handle situation on postgresql server-side, or
simply change fetching of string NULL into SQLMIX/sddpg driver.
The third solution to change my application behaviour was excluded (to much work).
It have seemed more robust for me to patch that inconsistency in sddpg.
Original DBF/CDX tables doesn't handle with null values. So, when I have started to changed data with SQL sources, my application didn't know how to handle those NIL values instead of empty string like it was when the data source was real DBF table.
There were two solutions:
To handle situation on postgresql server-side, or
simply change fetching of string NULL into SQLMIX/sddpg driver.
The third solution to change my application behaviour was excluded (to much work).
It have seemed more robust for me to patch that inconsistency in sddpg.
Here is relevant code:
https://github.com/hernad/harbour/blob/master/src/sddpg/core.c#L584