> > So given your experience (and getting back to the original discussion), > what is your take on strengthening support for JDBC's cursor update methods > in ResultSet? >
To be honest from a development point of view I've not yet done anything with jOOQ's current cursor implementation or JDBC's (read only or for update). Much of my time has been spent doing DBA/system roles, and coders opening up cursor for update has often been a DBA headache due to large numbers of records being locked during the life of the cursor - or the beautiful i/o storms caused by a cursor allowing a coder to traverse vast numbers of records (which they could never retrieve using a result set) to find what they are looking for and just about every time their answer has been 'it worked all right in development'. Shame that they used a test environment with 10,000 records, while the live system has 100M+. You may gather from the above, that I'm not the best person to ask about cursor usage - I do use them often directly in stored procedures and indirectly via other tools such as reporting and ETL libraries, but I've not coded with them directly for some time. -- 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/groups/opt_out.
