Re: [HACKERS] Regarding GSoc Application
От | Hitoshi Harada |
---|---|
Тема | Re: [HACKERS] Regarding GSoc Application |
Дата | |
Msg-id | CAP7QgmnUQq3QOHvKaXM+inxE3-U+RrTTy9e7xOGrRsJgV03dsQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] Regarding GSoc Application ("Atri Sharma" <atri.jiit@gmail.com>) |
Ответы |
Re: [HACKERS] Regarding GSoc Application
|
Список | pgsql-jdbc |
On Tue, Apr 10, 2012 at 8:41 PM, Atri Sharma <atri.jiit@gmail.com> wrote: > Hi All, > > I think we are back on the initial approach I proposed(hooking directly into > the JVM and executing Java code that calls JDBC).I think the best way to do > this is create a JVM that executes the Java code and give the control of the > JVM to the native API. > > I agree,the only need of Pl/Java that is apparent here is the need of the > Java internals(JDK et al).If we set them up independently,then,we can have > the FDW wrapping JDBC directly through JNI.JNI would call pure Java > functions to connect to the JDBC. > > I think we can proceed with this.Once we are done with the API calling Java > functions,I think the rest of the path is easily mapped(writing Java > functions to connect to JDBC). > > Please let me know your opinions on this. > I think Multicorn is a good example, which invokes Python from FDW routines though it is not using PL/Python. http://multicorn.org/ Thanks, -- Hitoshi Harada
В списке pgsql-jdbc по дате отправления: