Oliver Zeigermann wrote:
So, to get this going do you want me to prepare a patch for OJB which does exactly this: Introduce the createException method in the plattform class plus the exceptions and the initial code to feed it reasonably for Postgres, MySQL, SQLServer, and Sybase (is Sybase supported by OJB in the first place?)?
+1 this will great!
Will try, it might take some time...
No problem.
Maybe as a seconed step there could be a configuration mapping file ala Spring or Hibernate?
+1 This could be an option for OJB 1.1
Considering what you said, you could just throw the exceptions and the user decides if he/she wants to redo the transaction or if it is a real programming error. This way there would be no need for a configurable mapping...
ahh, misunderstand this. I thought user can configure which kind of exception will be thrown for an SQL error state, e.g. 345==>KeyKonstraintException.
regards, Armin
Oliver
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
