hi, I tried finding my answer by querying the posts here, but nothing quite 
jumped out.

I'm trying to write code that is transparent at least minimally across 
Oracle and PG but obviously it would be really nice gravy to get it across 
some of the other major enterprise RDMS at the very least MS Sequel Server.

The other issue to consider is that we plan to deploy over JRuby and are 
leveraging the Sequel JDBC drivers , so worst case for the scenario(s) that 
require the use of a cursor I can write code that is not so transparent  I 
would appreciate some pointers there if I do have to resort to that 
approach.

To  be clear , I want to be able to manage what records get faulted into 
memory for a given query i.e. just in case there's effectively some other 
mechanism that does as much but by another name,

thanks

-Charles

-- 
You received this message because you are subscribed to the Google Groups 
"sequel-talk" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/sequel-talk/-/Hjys-ERgh7sJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sequel-talk?hl=en.

Reply via email to