Can'i catch the contraints oracle with the FeatureWriter? I need to test the integrity of oracle and catch the exception and do something if an error occure.
Execution of statement `UPDATE "MYTABLE" SET "STATUT_PRP_R" = :"STATUT_PRP_R" WHERE "OBJECTID" = :"OBJECTID"' did not succeed; error was `ORA-02290: violation de contraintes (PRP_AQU_BORNEINCENDIE_P_CHK) de vérification'. (serverType=`...
Best answer by larry
View original
+16
The FeatureWriter itself can not catch the Oracle Constraints.
But using the AttributeValidator, you can filter a lot of invalid values before writing.
However, you still have to be aware of the different constraints in the Oracle database.
The FeatureWriter itself can not catch the Oracle Constraints.
But using the AttributeValidator, you can filter a lot of invalid values before writing.
However, you still have to be aware of the different constraints in the Oracle database.
Bonjour @mario_aylwin,
If you strictly depend on the database and you are building your queries dynamically, you can use a SQLExecutor instead of a FeatureWriter and check at the <Rejected> port for failed queries. The _reader_error attribute will have the error message from Oracle.
Example _reader_error value: An error occurred while accessing a table result for feature type `QueryFactory_SQLExecute'; message was `Execution of statement `INSERT INTO TABLE1 (COLUMN1) VALUES ('X')' did not succeed; error was `ORA-02290: check constraint (TEST.TABLE1_CHK1) violated'. (serverType=`ORACLE8i', serverName=`********', userName=`********', password=`***', dbname=`')' (server type is `ORACLE8i', server name is `*******', username is `*******', password is `***', database name is `')).
Bonjour @mario_aylwin,
If you strictly depend on the database and you are building your queries dynamically, you can use a SQLExecutor instead of a FeatureWriter and check at the <Rejected> port for failed queries. The _reader_error attribute will have the error message from Oracle.
Example _reader_error value: An error occurred while accessing a table result for feature type `QueryFactory_SQLExecute'; message was `Execution of statement `INSERT INTO TABLE1 (COLUMN1) VALUES ('X')' did not succeed; error was `ORA-02290: check constraint (TEST.TABLE1_CHK1) violated'. (serverType=`ORACLE8i', serverName=`********', userName=`********', password=`***', dbname=`')' (server type is `ORACLE8i', server name is `*******', username is `*******', password is `***', database name is `')).
Yes, i use that technique for now. But, it's not easy to use GEOMETRY with SQLExecutor.
An other solution to catch Oracle Constraint?
Yes, i use that technique for now. But, it's not easy to use GEOMETRY with SQLExecutor.
An other solution to catch Oracle Constraint?
+25
Yes, i use that technique for now. But, it's not easy to use GEOMETRY with SQLExecutor.
An other solution to catch Oracle Constraint?
+3
U can use a sql executor/creator to read out the user_constraints.
Query it for your table and constraint_name or just relevant table to get its constraint.
SELECT * FROM user_constraints
WHERE table_name = '<your table name>'
AND constraint_name = '<your constraint name>';
Then you can apply a test if the objects respect these.
Yes,
I use the transformer SQLExecutor and that functionne nicely.
Thanks every body.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
