Hi Sergi, you have spoken loud and clear. Good resume. But you don't think that UDFs without an shared variables space between SQL and UDF space are still very limited ? As I can see UDFs are limited to behave as static functions ( Invariant functions in IBM terminology ).
How to make this udfs collaborate with each others or leave some effect active for repetitive invocations. More even, that shared variables space can be used to simulate cursor implementation and useful for simplify column functions. regards, Dario. > Lets make some conclusions and start implementing. > I think plugins (with SPI) and java procedures which are stored as > bytecode or as jars in database are independent features. > And then automated loading of set of UDFs from jars into database can > be also represented as service which can be loaded via SPI mechanism. > So how I see this for the moment the needed services are: > 1) Database initialization service. It will do something on each > database creation (run initialization scripts and so on). > 2) Functions serivice. It will contain set of functions. But there > will be even no need to execute initialization scripts - they > will work like builtin H2 functions. > 3) Tables service. To allow user to create his own table > implementation best suited for his needs. > The last item is needed personally for me :) -- 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.
