We are using PowerBuilder 2019 R3 and recently,we have encountered an insert error message in the production environment when the end-user save the changes made.
Appendix: Details of root cause
The errors stem from, when PowerBuilder composes its SQL statements, the INSERTs now appear to get all columns in the datawindow, even those that we did not change a value for. If that value is NULL and the column is NOT NULL, that generates the error. My fix is to add INITIAL values to columns with database defaults. In previous PowerBuilder versions, these apparently were never in the INSERT statements at all; if they were, we would have gotten these error all along, going back to PowerBuilder 8.
Appreciate any thoughts or comments, and any possible solution.