Hi, I suggest to use only one statement per Statement.execute. This way your application is not dependent on a specific database (at least in this regard).
I would rather not support returning multiple result sets per statement in H2 if possible, because the potential benefit sounds too small compared to the implementation complexity. Regards, Thomas On Sun, Jun 17, 2012 at 9:51 PM, Noel Grandin <[email protected]> wrote: > On Sun, Jun 17, 2012 at 1:41 PM, Christopher Deckers <[email protected]> > wrote: >> >> I will keep it in mind, in case I get a bit of free time to play with >> H2 internals. By-the-way, any advices on where I should start, things >> to know, etc.? > > I think you'd need to start with the Parser class. That should be > straightforward, it's a manually coded recursive descent parser. > > The much harder part will be extending the Session class to cope with > multiple result sets. > > -- > You received this message because you are subscribed to the Google Groups "H2 > Database" group. > 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/h2-database?hl=en. > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. 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/h2-database?hl=en.
