hi!
--
You received this message because you are subscribed to the Google Groups "H2 Database" group.
To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-/17E6i7yUAnMJ.
To post to this group, send email to h2-da...@googlegroups.com.
To unsubscribe from this group, send email to h2-database...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
At that point I think we're outside the bounds of what H2 should
provide, and you should probably just implement that yourself in your
own main() function.
However, I'm happy to make some more of the AutoRegisterFunctionAliases
methods public again, if that will help?
> i also have in the queue stubs for all mysql 5.6 functions not
> implemented by h2.
>
Unless you actually have a use-case for those, I'd not be terribly keen
on cluttering up the code with them.
public static void register(Connection conn) throws SQLException
same as in org.h2.mode.FunctionsMySQL. Probably we want to add an interface that defines this method. Function names could be defined using an annotations, but the register method might be more flexible (allows to install triggers, create tables / views,...) so I think the register method would be nice.
For extensions that are to be auto-loaded when a certain mode is used, what about org.h2.ExtensionMySQL / ExtensionPostgreSQL / ExtensionOracle and so on.
Regards,
Thomas
then:for each $class{if $class instanceof org.h2.api.AggregateFunction{registerFunctionClass($class)}else{scan $class for methods starting with 'FN_'then registerFunctionMethod($class, $method, $fname)}}
for the MODE-Support already in H2 a filename like '/META-INF/org.h2.ext.FunctionClass.$MODE' could be used.
--
You received this message because you are subscribed to the Google Groups "H2 Database" group.
To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-/NXzf0yf1S8AJ.