Tested and confirmed, code displays correctly in the case of pgAdmin 1.14.3
in a UTF-8 encoded DB.
2012/9/11 Jon Garate
> Just tracked down the issue. The debugger won't display code if it
> contains characters with accent (in the case of spanish charset at least).
> ¿I guess this extends to the
Just tracked down the issue. The debugger won't display code if it contains
characters with accent (in the case of spanish charset at least). ¿I guess
this extends to the whole non-ascii charset? Other than that, looks good.
Thanks pgadmin-hackers!
2012/9/5 Dave Page
> On Wed, Sep 5, 2012 at 12:
On Wed, Sep 5, 2012 at 12:45 PM, Jon Garate wrote:
> I did so before testing master (which build a single .so file). In the case
> of the PRE_9_2 branch, I got 3 .so's
> When I updated the configuration to load those .so's I got a undefined
> symbol error when restarting PostgreSQL. Could it be th
I did so before testing master (which build a single .so file). In the case
of the PRE_9_2 branch, I got 3 .so's
When I updated the configuration to load those .so's I got a undefined
symbol error when restarting PostgreSQL. Could it be that I only need to
load a single .so in that case as well?
2
On Wed, Sep 5, 2012 at 12:31 PM, Jon Garate wrote:
> Hello dear list,
>
> I'm having trouble after setting up pldebugger git-current
> (eb754b6ba9a1c18e7bc4ddf521408be06768c697) commit in a Ubuntu 10.04.01
> x86_64 box. Server versión is 9.1.5.
> The issue is that once I start debugging a PLPgSQL
Hello dear list,
I'm having trouble after setting up pldebugger git-current
(eb754b6ba9a1c18e7bc4ddf521408be06768c697) commit in a Ubuntu 10.04.01
x86_64 box. Server versión is 9.1.5.
The issue is that once I start debugging a PLPgSQL function within pgAdmin,
once it goes one level down the call s
