Hi, > UDFs
I guess you mean user defined functions? > -- THIS ONE CAN'T BE USED - I dont know why ? I don't understand, why not? Does it throw an exception? > select a.* from LINKED_QUERY( > org.postgresql.Driver','jdbc:postgresql://127.0.0.1:5432/mydb','sa','********', > 'select * from mySchema.someTable' ) as a; > you must agree that isn't a nice syntax ;-) > and this is very redundant with LINKED TABLE's connections management. You could create a method to map a 'data source' to a connection: LINKED_DEFINE_DATASOURCE(dataSource, driver, url, user, password); LINKED_QUERY(dataSource, query); Or you could create a function that creates another function: LINK(dataSource, driver, url, user, password); This would then create the 'real' <dataSource>_QUERY alias. > many time we DON'T know in advance what need to be executed as > "CUSTOM SCRIPTS" that the us or final user can write in SQL as > application's customer procedures. I don't understand, how is that related to this problem? > I insist that almost anything is just inside H2: drivers and external > connections handling. As I wrote, it doesn't have high priority for me. I think it doesn't make sense to add functionality into the database engine itself if the same functionality can "live" outside. Unless many people need it. 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.
