Hi Aram, Sorry for the delay, and thanks for sharing your example.
Indeed, it's not out of the ordinary, yet it is a bit complex. As I thought before, this doesn't lend itself to a set of new features in the jOOQ loader API. I think it is best if the loader API just processes records that are already in the final form (give or take some data type conversions from number to string or vice versa). With jOOQ 3.8, there are now loadArrays(Stream) and loadRecords(Stream) methods, which consume a Java 8 Stream. This could be useful to pass a Stream pipeline directly to the loader, which then executes it to consume individual rows. But you can of course do everything "outside" of jOOQ as you're doing now. Lukas 2016-06-12 14:43 GMT+02:00 Aram Mirzadeh <[email protected]>: > > It isn't anything abnormal, just a lot of processing. BIRT was considered > at one point. > > The business logic layer consists of reading each item (CSVItem row - a > row from a sales entry system) > > 1 & 2) Normalizing the values in some fields. > 3) Finding the monies conversation equivalence of cost and price to a > single currency. > 5) Applying 200-230 regex expressions to exclude some line items.- concat > results of rules in a field. > 6) Applying 30-40 regex expressions to to assign "item category"- set > result in a field > 7) Persist to the database.(all items) > > The final step involves building some views using GROUP_CONCAT of the > country/item categories of "accepted items" to do some pivot tables in an > excel workbook. > > Aram > > On Sunday, June 12, 2016 at 4:02:34 AM UTC-4, Lukas Eder wrote: >> >> >> >> 2016-06-12 9:34 GMT+02:00 Aram Mirzadeh <[email protected]>: >>> >>> No you're right as far as doing it manually vs. a mapper is probably not >>> much of a time saver but it's easier to read IMHO. >>> >> >> Well, there's a tradeoff... Readability and complex business logic. I >> suspect you'll need to pick one :) >> >> Of course, if you're interested in sharing a bit more about that business >> logic, perhaps, there's a low hanging fruit where I could help find a >> simple solution, or perhaps improve the jOOQ APIs... Just let me know if >> you want to push further on this. >> >> Lukas >> > -- > 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. > -- 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.
