Ishikawa Toshiyuki wrote:
> Hi, all
>
> I've downloaded EnterpriseDB Advanced Server 8.2 for Windows
> New! (23-Apr-2007) version and ran Developer Studio 8.2 to
> see Debugger. I have several functions that were used to make
> a textbook to teach PL/pgSQL in the organization I am involved,
> i.e
Hi, all
I've downloaded EnterpriseDB Advanced Server 8.2 for Windows
New! (23-Apr-2007) version and ran Developer Studio 8.2 to
see Debugger. I have several functions that were used to make
a textbook to teach PL/pgSQL in the organization I am involved,
i.e., same to Hiroshi's, and manipulated wi
Guillaume Lelarge wrote:
> It took me some time to make it work : downloading EnterpriseDB Advanced
> Server, downloading an EnterpriseDB compatible distro (or better, a
> vmware image), installing the termcap library, installing EntrepriseDB
> (nice installer BTW), configuring and launching it...
Guillaume Lelarge a écrit :
Dave Page a écrit :
Guillaume Lelarge wrote:
Yesterday, I downloaded the client, which was really silly. But I
don't find any debugger module on the enterprisedb website. I thought
I just needed a module to insert on a vanilla PostgreSQL... and
pgAdmin of course.
Dave Page a écrit :
Guillaume Lelarge wrote:
Yesterday, I downloaded the client, which was really silly. But I
don't find any debugger module on the enterprisedb website. I thought
I just needed a module to insert on a vanilla PostgreSQL... and
pgAdmin of course.
The plugin should be relea
Guillaume Lelarge wrote:
Yesterday, I downloaded the client, which was really silly. But I don't
find any debugger module on the enterprisedb website. I thought I just
needed a module to insert on a vanilla PostgreSQL... and pgAdmin of course.
The plugin should be released in the not-to-dist
Dave Page a écrit :
Guillaume Lelarge wrote:
Dave Page a écrit :
I've now completed the integration of the debugger with pgAdmin - it
was somewhat easier than I'd expected :-)
Can those of you with access to a copy of EnterpriseDB please give it
a try and report any issues. If you feel like
Guillaume Lelarge wrote:
Dave Page a écrit :
I've now completed the integration of the debugger with pgAdmin - it
was somewhat easier than I'd expected :-)
Can those of you with access to a copy of EnterpriseDB please give it
a try and report any issues. If you feel like downloading a copy to
Dave Page a écrit :
I've now completed the integration of the debugger with pgAdmin - it was
somewhat easier than I'd expected :-)
Can those of you with access to a copy of EnterpriseDB please give it a
try and report any issues. If you feel like downloading a copy to play
with, you can get d
Hi,
I've now completed the integration of the debugger with pgAdmin - it was
somewhat easier than I'd expected :-)
Can those of you with access to a copy of EnterpriseDB please give it a
try and report any issues. If you feel like downloading a copy to play
with, you can get downloads from
Florian G. Pflug wrote:
Maybe removing those libs from the output of pg_config that
we surely don't need or want (like -lpgport) is workable
alternative?
Yeah, that sounds reasonable.
I'll try to do that, and try to cleanup that part of acinclude.m4.
Thanks :-)
Regards, Dave
-
Dave Page wrote:
Florian G. Pflug wrote:
Dave Page wrote:
Florian G. Pflug wrote:
I'm currently thinking that unconditionally adding the output
of pg_config --libs to LIBS if linking statically might
be a better approach - thoughts?
That whole section of the file seems a bit kooky to me - it
Florian G. Pflug wrote:
> Dave Page wrote:
>> Florian G. Pflug wrote:
>>> I'm currently thinking that unconditionally adding the output
>>> of pg_config --libs to LIBS if linking statically might
>>> be a better approach - thoughts?
>>
>> That whole section of the file seems a bit kooky to me - it
Dave Page wrote:
Florian G. Pflug wrote:
I'm currently thinking that unconditionally adding the output
of pg_config --libs to LIBS if linking statically might
be a better approach - thoughts?
That whole section of the file seems a bit kooky to me - it does some
weird stuff on Solaris as well.
Florian G. Pflug wrote:
> Dave Page wrote:
>> Florian G. Pflug wrote:
>>> BTW, I've been working on an i386 binary of pgadmin3 that is statically
>>> linked.
>>> If've managed to compile static version of libxml, libxslt, wxwidgets
>>> and
>>> libpq, but configure fails for pgadmin3 because it does
Dave Page wrote:
Florian G. Pflug wrote:
BTW, I've been working on an i386 binary of pgadmin3 that is statically
linked.
If've managed to compile static version of libxml, libxslt, wxwidgets and
libpq, but configure fails for pgadmin3 because it doesn't know that it has
to pass "-lssl" when link
Florian G. Pflug wrote:
> Dave Page wrote:
>> The existing complete-bundle.sh code works fine, and rewrites the paths
>> to the wx libraries as expected, however the debugger crashes when run.
>> As best I can figure, this is because although the debugger has the
>> correct relative paths to the li
Dave Page wrote:
The existing complete-bundle.sh code works fine, and rewrites the paths
to the wx libraries as expected, however the debugger crashes when run.
As best I can figure, this is because although the debugger has the
correct relative paths to the libraries, some of those (wx) librarie
Dave Page wrote:
> I'd be happy to go with the embedded bundle option - what puts me off is
> that I'm still not overly confident with make etc. The merged code
> option is nicest in theory, but I'd be concerned that it would always
> seem like bolted on code without an almost complete rewrite (wh
Florian G. Pflug wrote:
Dave Page wrote:
Hiroshi Saito wrote:
Umm, There may also be structure which debugger is connected with
PostgreSQL by itself and waits for a response, and it may not be
desirable on a constitution.
Yeah, that's a good point. In case that doesn't retranslate to German
Hi Florian-san.
debugger operates very wonderful by EnterpriseDB now. However, some functions
for the operation still run short by the OSS-PostgreSQL version. Then, Korry-san
will realize it soon. And the specification is very great. The specification of debugger
contains the minimum for alrea
Dave Page wrote:
Hiroshi Saito wrote:
Umm, There may also be structure which debugger is connected with
PostgreSQL by itself and waits for a response, and it may not be
desirable on a constitution.
Yeah, that's a good point. In case that doesn't retranslate to German
well, what Hiroshi is sa
Hiroshi Saito wrote:
Umm, There may also be structure which debugger is connected with
PostgreSQL by itself and waits for a response, and it may not be
desirable on a constitution.
Yeah, that's a good point. In case that doesn't retranslate to German
well, what Hiroshi is saying is that users
From: "Florian G. Pflug" <[EMAIL PROTECTED]>
Dave Page wrote:
Hi all,
So far, the code has been modified mainly to get rid of it's use of MDI
windows, and to use wxAUI instead, and to integrate it into the pgAdmin
build system.
Cool.
:-)
Having tried it on OS X, I find we have a problem.
Florian G. Pflug wrote:
The final option (which I am currently favouring) would be to move the
debugger code into pgAdmin itself, rather than keeping it as a separate
application. This has the disadvantage that the architecture if the
debugger is quite different from pgAdmin, so whilst it could w
Dave Page wrote:
Hi all,
So far, the code has been modified mainly to get rid of it's use of MDI
windows, and to use wxAUI instead, and to integrate it into the pgAdmin
build system.
Cool.
Having tried it on OS X, I find we have a problem. On that platform,
executables are distributed inside
Hi all,
At Hiroshi's request I've just been testing the pl/pgsql debugger that
he's been working on under OS X (For those that don't know, EnterpriseDB
donated their wxWidgets based prototype debugger to us under our normal
licence).
So far, the code has been modified mainly to get rid of it's us
27 matches
Mail list logo
