0

With Sybase Central I've configured a MobiLink test object, where I'm trying to detect a unique constrain violation before uploading. Unfortunately it appears upload_fetch_column_conflict​ seems to not being executed. My events are configured like this on Sybase Central:

[...]
​Product (DBA): upload_fetch_column_conflict​
SELECT "DBA"."Product"."name",
    "DBA"."Product"."quantity",
    "DBA"."Product"."quality"
FROM "DBA"."Product"
WHERE "DBA."Product"."name" = {ml r."name} AND NOT (SELECT count(*) from "DBA"."Product" WHERE quality = {ml r.quality})> 0;
[...]

Any idea what I've maybe missed?

1 Answer 1

0

upload_fetch_column_conflict is only getting called, if there is a line updated. Therefore an insert will not trigger that function.

If inserting a new line which might conflict with a recent change on consolidated database, the conflict needs to be caught during upload workflow -- so e.g. inside processing of upload_insert.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.