Marc G. Fournier wrote:
On Sat, 2 Apr 2005, Dave Cramer wrote:
pl-j ( the other java procedural language ) is definately interested
in being in core.
So your objectives has changed then? As I recall it, Laszlo thought it
important to keep some level of database independence with PL/J and
didn't
d) Bringing PL/Java into core will force a consistent documentation
and, I imagine, a chapter of it's own in the main docs. I'm happy
to write most of it but English is not my native language. Whatever
I put into print will always benefit from a review.
There is nothing stop'ng a chapter being adde
On Sat, 2 Apr 2005, Joshua D. Drake wrote:
Peter Eisentraut wrote:
Joshua D. Drake wrote:
Actually as I think about it... that is not the case even now. When
we download the php source the base configure before compile is:
./configure --disable-all
Thus no use of PostgreSQL whatsoever.
I'm sure it
Peter Eisentraut wrote:
Joshua D. Drake wrote:
Actually as I think about it... that is not the case even now. When
we download the php source the base configure before compile is:
./configure --disable-all
Thus no use of PostgreSQL whatsoever.
I'm sure it is possible to get around it manual
On Sat, 2 Apr 2005, Peter Eisentraut wrote:
Rod Taylor wrote:
There is nothing stopping additional links to documentation from
being added to the PostgreSQL website in the documentation section.
That is true, but that does not foster consistent documentation, which
is what Thomas Hallgren wanted.
I
Rod Taylor wrote:
> There is nothing stopping additional links to documentation from
> being added to the PostgreSQL website in the documentation section.
That is true, but that does not foster consistent documentation, which
is what Thomas Hallgren wanted.
--
Peter Eisentraut
http://developer.
On Sat, 2005-04-02 at 21:48 +0200, Peter Eisentraut wrote:
> Marc G. Fournier wrote:
> > > d) Bringing PL/Java into core will force a consistent documentation
> > > and, I imagine, a chapter of it's own in the main docs. I'm happy
> > > to write most of it but English is not my native language. Wha
Marc G. Fournier wrote:
> > d) Bringing PL/Java into core will force a consistent documentation
> > and, I imagine, a chapter of it's own in the main docs. I'm happy
> > to write most of it but English is not my native language. Whatever
> > I put into print will always benefit from a review.
>
> T
On Sat, 2 Apr 2005, Thomas Hallgren wrote:
b) I've been forced to do pull some tricks in PL/Java to work around things
that I consider lacking in the interfaces. Having PL/Java in core would make
it possible to work together more tightly in order to find good
solutions/API's that can benefit all
Thomas Hallgren wrote:
Tom Lane wrote:
are a few features shy of a load already. I'm pretty sure pl/r and
pl/java will need changes to support this feature too. If they were in
core CVS then I'd consider it part of my responsibility to fix 'em
... but they aren't, so it isn't my problem, so it f
Joshua D. Drake wrote:
> Actually as I think about it... that is not the case even now. When
> we download the php source the base configure before compile is:
>
> ./configure --disable-all
>
> Thus no use of PostgreSQL whatsoever.
I'm sure it is possible to get around it manually, but think about
On Sat, 2 Apr 2005, Peter Eisentraut wrote:
Joshua D. Drake wrote:
Oh you do need PHP installed you just don't need the source. As
everyone knows ;) I am not a c-programmer and I do not know the finer
details. I can of course find out from my developers.
Well, that doesn't solve the circular build
Joshua D. Drake wrote:
> Oh you do need PHP installed you just don't need the source. As
> everyone knows ;) I am not a c-programmer and I do not know the finer
> details. I can of course find out from my developers.
Well, that doesn't solve the circular build dependency issue then.
Before you c
On Sat, 2 Apr 2005, Peter Eisentraut wrote:
Joshua D. Drake wrote:
I am not sure I understand the question but we are
linking against the .so now. So as long as PHP
is and PostgreSQL ./configure knows where to look
we should be good.
The question is, how can you build a PL/something module without
Joshua D. Drake wrote:
> I am not sure I understand the question but we are
> linking against the .so now. So as long as PHP
> is and PostgreSQL ./configure knows where to look
> we should be good.
The question is, how can you build a PL/something module without having
"something" installed at bu
Peter Eisentraut wrote:
Joshua D. Drake wrote:
We at Command Prompt are in the process of completing
a new rev of plPHP. The new rev will not require the
PHP source. It will only require that PHP is installed.
How can that be?
I am not sure I understand the question but we are
linking ag
Tom Lane wrote:
Peter Eisentraut <[EMAIL PROTECTED]> writes:
I'm not convinced that PLs are more tied to the core than say OpenFTS,
and if we can't maintain that kind of thing externally, then this whole
extension thing sounds like a failure to me.
It's *possible* to do it. Whether it's a net s
Joshua D. Drake wrote:
> We at Command Prompt are in the process of completing
> a new rev of plPHP. The new rev will not require the
> PHP source. It will only require that PHP is installed.
How can that be?
> Are we interested in having plPHP in core?
Personally, I'm not too excited about it.
Alvaro Herrera wrote:
On Fri, Apr 01, 2005 at 07:11:14PM -0800, Joshua D. Drake wrote:
Hi Joshua,
We at Command Prompt are in the process of completing
a new rev of plPHP. The new rev will not require the
PHP source. It will only require that PHP is installed.
In other words it can be installed
On Fri, Apr 01, 2005 at 07:11:14PM -0800, Joshua D. Drake wrote:
Hi Joshua,
> We at Command Prompt are in the process of completing
> a new rev of plPHP. The new rev will not require the
> PHP source. It will only require that PHP is installed.
>
> In other words it can be installed just like an
20 matches
Mail list logo
