Anyone Recognize Error?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Anyone Recognize Error?

nolasco
Hi.

We just patched our Informix database to the latest patch level and now one of our VASmalltalk (V8.0.1) apps is producing this error during database inserts:

    ABT.DBB.2.e: Null assignment to a non-null field.


Frankly I am lost trying to figure out what is triggering this and am hoping that someone else has seen this before.


--
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/-/QdW5fmEY5b0J.
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.
Reply | Threaded
Open this post in threaded view
|

Re: Anyone Recognize Error?

Wayne Johnston
Is this the error you'd expect to get (somewhere) when you perform an SQL INSERT statement but don't give a value for a non-nullable column in the table?

--
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/-/l_jq8iI11d4J.
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.
Reply | Threaded
Open this post in threaded view
|

Re: Anyone Recognize Error?

nolasco
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.