I have been chasing an out of memory situation in my app, which uses the H2 database, and I got it narrowed down to one statement in ActiveRecord-JDBC:
SELECT IDENTITY() FROM items; Result: IDENTITY() 0 0 0 (more rows with same value continues...) In H2, the above statement seems to return a result set that has length equal to that of the entire table (in this case, a single column called IDENTITY(), with as many rows as the table itself). The items table contains tens of thousands of entries and it quickly consumes all the memory while executing this particular query. I don't know very much about SQL, so is this a bug in H2 for returning so many rows, or a bug in ActiveRecord-JDBC in using SELECT IDENTITY(), rather than CALL IDENTITY()? (Or a bug in me?). Peter _______________________________________________ Jruby-extras-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/jruby-extras-devel
