Hello, I understand your arguments. Yes, the well-known Row interface is missing from the JDBC API (as are many other types). It would be the correct type to pass to a trigger. I wonder what would be required to form an expert group to finally fix all those JDBC API blunders...
Anyway, I will stop insisting :-) Am Montag, 18. März 2013 19:14:04 UTC+1 schrieb Thomas Mueller: > > Hi, > > I would like to keep the current behavior of the TriggerAdapter's > ResultSet. The TriggerAdapter should be as convenient as possible (that's > the reason to have it), and having to call next() isn't convenient. I would > like to use the ResultSet interface because it's a known API to work with > rows (there is no well known Row interface). > > What we could do is throw an exception when trying to call next(). This > also doesn't match the general contract of a ResultSet however. Or, return > false when calling next(). > > Regards, > Thomas > > > On Sunday, March 17, 2013, Noel Grandin wrote: > >> TriggerAdapter is a __convenience__ interface. >> >> Don't use it you don't like it, rather just use the Trigger interface >> directly. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "H2 Database" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/h2-database?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
