Comments on: DB Triggers and JPA http://itknowledgeexchange.techtarget.com/itanswers/db-triggers-and-jpa/ Sun, 19 May 2013 03:14:28 +0000 hourly 1 By: tomliotta http://itknowledgeexchange.techtarget.com/itanswers/db-triggers-and-jpa/#comment-74020 tomliotta Sat, 20 Feb 2010 10:43:00 +0000 #comment-74020 If you can demonstrate that the file insert happened and the trigger did not fire, that would call for an immediate problem report to IBM. Personally, I find it very unlikely. Most likely, the trigger logic is indeed incorrect or authority is inappropriate. If triggers failed to fire, IBM Support lines would be burning up.

Tom

]]> By: rdgrimes http://itknowledgeexchange.techtarget.com/itanswers/db-triggers-and-jpa/#comment-50552 rdgrimes Fri, 09 Nov 2007 23:38:08 +0000 #comment-50552 I finally gave up on using a trigger program. Instead I decided to write a java class that uses ProgramCall from the com.ibm.as400.access package. I have ProgramCall execute an iSeries CLP program that, in turn, calls QSYGETPH and QSYRLSPH to validate the user credentials and return a valid/not valid flag. This seems to work just fine for what I’m doing.

R. Grimes

]]> By: rdgrimes http://itknowledgeexchange.techtarget.com/itanswers/db-triggers-and-jpa/#comment-50548 rdgrimes Thu, 08 Nov 2007 21:26:57 +0000 #comment-50548 I’m using the same connection User ID and Password as worked on the old non-jpa architecture. Also, since I can see the record getting dropped into the database, there is obviously no problem with my write authority. It’s the db’s responsibility to detect a inserted record and fire the trigger. But, this is acting as though an insert via jpa is operating under stealth.

R. Grimes

]]>