That's what I initially thought. But, all fields at the destination table allow nulls.
Here's the kicker. The data to be inserted came from a SQL statement that was a UNION of 7 other SQL statements. But, when I decided to break up this statement into it's 7 individual parts and performed the insert after the data for each part was retrieved, the error just disappeared! As such, I was suspecting that there was something about the UNION that was causing the error post-patch. I know it's not the size of the result set because I have other SQL statements that return much larger results.
It's a really strange behavior.
--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/va-smalltalk/-/3YLW0sYHZp8J.
To post to this group, send email to
[hidden email].
To unsubscribe from this group, send email to
[hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.