Hi, Thanks for your questions. I'm happy to hear that you've been mostly successful with jOOQ thus far. I will comment inline:
2017-11-09 15:51 GMT+01:00 BoPe86 <[email protected]>: > I naively tried this for inserting 2 rows at once: > > Insertdataprocedure p = new Insertdataprocedure(); > > p.setInName("John"); > p.setInSurname("Doe"); > p.setInName("Someone"); > p.setInSurname("Else"); > > hoping "p" will just append parameters and execute procedure once while > inserting 2 sets of data, but no luck :( > That's an intereting assumption, but no, the "p" reference is a reference to a stored procedure call that you're going to make. It contains a set of input parameters and a set of output parameters, but no notion of sequential calls. > What's the proper way of calling stored procedures in batched manner using > JOOQ? > There currently is none, and I must admit, I have not yet come across a use-case where stored procedures would be called in a batch. Usually, people would write anonymous blocks (e.g. PL/SQL BEGIN .. END blocks) that dynamically call a set of stored procedures. Alternatively, there would be a staging temp table that contains all the data, and then a procedural loop would batch those calls directly in the database. Would you mind describing this use-case a bit? Are you trying to save bandwidth between client and server for consecutive procedure calls? Thanks, 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.
