Hi, Right now I'm against applying the patch. I would like to keep the internals of the database internal. It seems to me creating a public API for the AST would open a big can of worms, for example it would mean we need to maintain backward compatibility, we would need documentation, we would be less flexible to change it.
I don't currently see the use case. Why would you want to manipulate the AST _outside_ of the database? It sounds like you want to add more features to the database, but don't want to actually contribute them to the database itself. That sounds wrong. Regards, Thomas On Tue, Apr 23, 2013 at 2:24 AM, Ashwin Jayaprakash < [email protected]> wrote: > Hi, I managed to setup the H2 Dev environment (really easy, hat tip to > Thomas) and patch the org.h2.command.dml.Select class to address the gaps > I was talking about earlier. > > Pls review the patch attached with a simple test class. It has some dead > simple getter method fixes. If this looks good, I hope you guys can > integrate it with the H2 Trunk. > > > Thanks! > > -- > 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-US. For more options, visit https://groups.google.com/groups/opt_out.
