1. ALEXANDER TAPIA
  2. PowerBuilder
  3. Saturday, 8 June 2024 11:17 AM UTC

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.


 

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Saturday, 8 June 2024 12:45 PM UTC
  2. PowerBuilder
  3. # 1

Hi Alexander;

  This sounds like a change to the DBMS environment. Either a DBMS software upgrade or schema changes that now are enforcing these new rules. If so, then the DWO's need to make sure that the Null defaults are addressed. Your idea on using initial default values is a good plan to address this.

Regards ... Chris 

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.