Re: [HACKERS] pljava revisited

2003-12-12 Thread Bruce Momjian
Peter Eisentraut wrote: > Tom Lane wrote: > > libpq++ got heaved overboard largely > > because the autoconf burden for it was too high, > > That's news to me. Certainly the overhead doesn't grow smaller by > splitting stuff up in smaller pieces. Yea, now there is no configure for libpq++ at all

Re: [HACKERS] pljava revisited

2003-12-12 Thread Thomas Hallgren
The sqlstandards.org is still down I think. Is this something new in the upcoming 200x spec? I could not see it mentioned in the SQL-99. I'm a great fan of standards. If there is one I'll make my pljava adhere to it. Any information on this topic is greatly appreciated. Thanks, - thomas "Peter

Re: [HACKERS] pljava revisited

2003-12-11 Thread Peter Eisentraut
Andrew Dunstan wrote: > Peter Eisentraut wrote: > >Thomas Hallgren wrote: > >>What are your thoughts and ideas? > > > >Instead of making up your own stuff, there's a whole SQL standard > > that tells you how Java embedded in an SQL server should work. Of > > course that doesn't tell you about impl

Re: [HACKERS] pljava revisited

2003-12-11 Thread Andrew Dunstan
Peter Eisentraut wrote: Thomas Hallgren wrote: What are your thoughts and ideas? Instead of making up your own stuff, there's a whole SQL standard that tells you how Java embedded in an SQL server should work. Of course that doesn't tell you about implementation details. Where can

Re: [HACKERS] pljava revisited

2003-12-11 Thread Peter Eisentraut
Thomas Hallgren wrote: > What are your thoughts and ideas? Instead of making up your own stuff, there's a whole SQL standard that tells you how Java embedded in an SQL server should work. Of course that doesn't tell you about implementation details. ---(end of broadcas

Re: [HACKERS] pljava revisited

2003-12-11 Thread Peter Eisentraut
Tom Lane wrote: > libpq++ got heaved overboard largely > because the autoconf burden for it was too high, That's news to me. Certainly the overhead doesn't grow smaller by splitting stuff up in smaller pieces. ---(end of broadcast)--- TIP 4: Don'

Re: [HACKERS] pljava revisited

2003-12-10 Thread Thomas Hallgren
Two comments. Context switches are of course much cheaper then loading a JVM. No argument there. The point is that the JVM is loaded once for each connection (when the connection makes the first call to a java function). Millions of calls may follow that reuses the same JVM. Each of those calls wil

Re: [HACKERS] pljava revisited

2003-12-10 Thread ow
--- Thomas Hallgren <[EMAIL PROTECTED]> wrote: > The JVM will be started on-demand. > Although I realize that one JVM per connection will consume a fair amount of > resources, I still think it is the best solution. The description of this > system must of course make it very clear that this is wha

Re: [HACKERS] pljava revisited

2003-12-10 Thread Robert Treat
On Wed, 2003-12-10 at 13:04, Jan Wieck wrote: > Andrew Rawnsley wrote: > > >> Other pl* (perl, python, tcl) languages have vanilla C glue code. > >> Might be better to stick to this. If you aren't using advanced C++ > >> features that shouldn't be too hard - well structured C can be just as > >

Re: [HACKERS] pljava revisited

2003-12-10 Thread Tom Lane
Andrew Dunstan <[EMAIL PROTECTED]> writes: > Thomas Hallgren wrote: >> C++ or C is not a big issue. I might rewrite it into pure C. The main reason >> for C++ is to be able to use objects with virtual methods. I know how to do >> that in C too but I don't quite agree that its "just as clean" :-) >

Re: [HACKERS] pljava revisited

2003-12-10 Thread Jan Wieck
Andrew Rawnsley wrote: Other pl* (perl, python, tcl) languages have vanilla C glue code. Might be better to stick to this. If you aren't using advanced C++ features that shouldn't be too hard - well structured C can be just as readable as well structured C++. At the very lowest level, about the

Re: [HACKERS] pljava revisited

2003-12-10 Thread Andrew Rawnsley
On Dec 10, 2003, at 1:51 PM, Andrew Dunstan wrote: Thomas Hallgren wrote: The JVM will be started on-demand. Although I realize that one JVM per connection will consume a fair amount of resources, I still think it is the best solution. The description of this system must of course make it very

Re: [HACKERS] pljava revisited

2003-12-10 Thread Andrew Dunstan
Thomas Hallgren wrote: The JVM will be started on-demand. Although I realize that one JVM per connection will consume a fair amount of resources, I still think it is the best solution. The description of this system must of course make it very clear that this is what happens and ultimately provide

Re: [HACKERS] pljava revisited

2003-12-10 Thread Thomas Hallgren
The JVM will be started on-demand. Although I realize that one JVM per connection will consume a fair amount of resources, I still think it is the best solution. The description of this system must of course make it very clear that this is what happens and ultimately provide the means of tuning the

Re: [HACKERS] pljava revisited

2003-12-10 Thread Andrew Rawnsley
On Dec 10, 2003, at 11:23 AM, Andrew Dunstan wrote: Thomas Hallgren wrote: Hi, I'm working on a new pl/java prototype that I hope will become production quality some time in the future. Before my project gets to far, I'd like to gather some input from other users. I've taken a slightly differen

Re: [HACKERS] pljava revisited

2003-12-10 Thread Andrew Dunstan
Thomas Hallgren wrote: Hi, I'm working on a new pl/java prototype that I hope will become production quality some time in the future. Before my project gets to far, I'd like to gather some input from other users. I've taken a slightly different approach than what seems to be the case for other att

[HACKERS] pljava revisited

2003-12-10 Thread Thomas Hallgren
Hi, I'm working on a new pl/java prototype that I hope will become production quality some time in the future. Before my project gets to far, I'd like to gather some input from other users. I've taken a slightly different approach than what seems to be the case for other attempts that I've managed