Hi, As for me issue 3 is definitely a bug. But this happens because CALL statement translates elements of array result to columns. For example: CALL (1,2,3) will return row with 3 columns. Indeed this behavior was introduced before me (see rev. 2427 Call.query) and I'm not a fan of this feature at all too but I've kept backward compatibility at time of my changes.
regards, Sergi On Mar 24, 9:16 am, Thomas Mueller <[email protected]> wrote: > Hi, > > > What do you think about issue 3, though? That looks like a bug, though. > > This is actually on purpose: each element is returned as its own > 'column'. I didn't implement that, it was Sergi Vladykin. > > Please tell me if it's a (compatibility) problem. I'm not a big fan of > this 'feature'. > > Regards, > Thomas -- 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.
