Hi Lukas There are many reasons which might make it difficult to use a stored procedure
- Unit-Testability of the code - Reuse of existing Java code modules - Complicated business logic on the way from source records to destination records - Different databases in development and production - Missing knowhow to maintain PL/SQL just to name a few. Taking the mentioned real-world usecase as an example: In this case the exact content of the history entries are assembled from a dynamic Excel template using the openL rule engine. This is Java technologie without an alternative in PL/SQL. Regards, Jan -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
