Assume we have a CONNECT JDBC table called ProductVariants. I can successfully issue the following command:
The above works with hard coded values when issued direct, works when issued via a stored procedure, but does NOT work when issued via a trigger (on another table). With the trigger you get the following error:
Of course hard coded values are useless, what I was originally trying to do via a trigger was the following:
where v_new_qty and v_ProductVariantId are declared as BIGINT and so are the corresponding connect columns. This command produces different errors depending on if issued via a trigger or stored procedure. When issued via a trigger the error is:
When I call a stored procedure and pass in the values the error is:
In the stored procedure scenario it looks like it is somehow not seeing the variables. In the trigger case I have no idea.
This is in a critical code path for a client deployment unfortunately, and we can't find a work around so a bug fix is critical for us.