> -Original Message-
> From: Merlin Moncure [mailto:[EMAIL PROTECTED]
> Sent: 16 March 2005 17:20
> To: Dave Page
> Cc: pgadmin-hackers@postgresql.org; pgadmin-hackers@postgresql.org
> Subject: RE: [pgadmin-hackers] prevent users from seeing
> pl/pgsql code in pgadmin
>
>
> What abou
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Florian G. Pflug
> Sent: 13 March 2005 13:57
> To: pgadmin-hackers@postgresql.org
> Subject: Re: [pgadmin-hackers] [PATCH] Various OSX fixes &
> .app bundle building
>
> Sorry for replying to my
Thanks Florian, patches applied.
Regards, Dave.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Florian G. Pflug
> Sent: 12 March 2005 16:41
> To: pgadmin-hackers@postgresql.org
> Subject: [pgadmin-hackers] [PATCH] Various OSX fixes & .app
> b
Log Message:
---
Fix some tabs that my editor converted to spaces.
Modified Files:
--
pgadmin3:
Makefile.am (r1.36 -> r1.37)
Index: Makefile.am
===
RCS file: /projects/pgadmin3/Makefile.am,v
retrieving
Log Message:
---
I wanted to build a .app bundle for pgadmin, but I found no support
for this in the build system. I added an option --build-bundle that
basically overwrites --prefix to $(pwd)tmp, and added a PgAdminIII.app
target to Makefile.am. The built bundle includes the pgadmin3 bin
Update of /projects/pgadmin3/pkg/mac
In directory developer.pgadmin.org:/tmp/cvs-serv15105/mac
Log Message:
Directory /projects/pgadmin3/pkg/mac added to the repository
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send a
Log Message:
---
Fix for non-SSL enabled libpq builds [Florian G. Pflug]
Modified Files:
--
pgadmin3:
CHANGELOG.txt (r1.192 -> r1.193)
pgadmin3/src/db:
pgConn.cpp (r1.64 -> r1.65)
pgadmin3/src/include:
pgConn.h (r1.30 -> r1.31)
Index: CHANGE
Log Message:
---
Mask the password on the main tab of the user properties dialogue [Hiroshi
Saito] (again - arrgh, I'm losing it!!)
Modified Files:
--
pgadmin3/src/include:
dlgUser.h (r1.16 -> r1.17)
pgadmin3/src/ui:
dlgUser.cpp (r1.38 -> r1.39)
pga
Log Message:
---
Mask the password on the main tab of the user properties dialogue [Hiroshi
Saito]
Modified Files:
--
pgadmin3:
Makefile.am (r1.34 -> r1.35)
acinclude.m4 (r1.42 -> r1.43)
configure.ac (r1.33 -> r1.34)
pgadmin3/src/include:
> -Original Message-
> From: Hiroshi Saito [mailto:[EMAIL PROTECTED]
> Sent: 16 March 2005 17:42
> To: Dave Page; Andreas Pflug
> Cc: pgadmin-hackers@postgresql.org
> Subject: Re: Again, the requirement of password of dlgUser.cpp
>
> Hi Dave.
>
> > OK, I'll agree with that - the passw
From: "Andreas Pflug" <[EMAIL PROTECTED]>
>
> I however don't see a need for a duplicate input. If in doubt, it can be
> checked.
No, fellow watching it behind you.
regards,
Hiroshi Saito
---(end of broadcast)---
TIP 2: you can get off all lists
Dave Page wrote:
I see no reason /not/ to include this patch - especially as Hiroshi has had
multiple requests for it (as have I in the past).
I will properly review it as soon as I can.
I however don't see a need for a duplicate input. If in doubt, it can be
checked.
Regards,
Andreas
--
-Original Message-
From: Andreas Pflug [mailto:[EMAIL PROTECTED]
Sent: Wed 3/16/2005 5:44 PM
To: Hiroshi Saito
Cc: Dave Page; pgadmin-hackers@postgresql.org
Subject: Re: [pgadmin-hackers] Again, the requirement of password of dlgUser.cpp
Hiroshi Saito wrote:
>>2) Because it cannot be
From: "Andreas Pflug" <[EMAIL PROTECTED]>
> Dave Page wrote:
> >
> > I hope they like it - they certainly haven't objected yet!! :-)
>
> I *do* like it, except for the turtle, esp. since I know now where it
> comes from :-)
Seems you that turtle is me. Every time pgAdmin is used, it appears,
From: "Andreas Pflug" <[EMAIL PROTECTED]>
> Hiroshi Saito wrote:
>
> >>2) Because it cannot be seen anymore, it should be confirmed
>
>
>
> Just look at the SQL page...
Um, User knows how to use pgAdmin, and he won't particularly see it.
In the input of the password. Probably.
regards,
Dave Page wrote:
I hope they like it - they certainly haven't objected yet!! :-)
I *do* like it, except for the turtle, esp. since I know now where it
comes from :-)
Regards,
Andreas
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands
Hiroshi Saito wrote:
2) Because it cannot be seen anymore, it should be confirmed
Just look at the SQL page...
Regards,
Andreas
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Hi Dave.
> OK, I'll agree with that - the password is not shown in the SQL pane by
> default these days.
>
> However - we need to improve your patch Hiroshi:
>
> 1) You should add the style to txtPasswd, not stPasswd :-)
Uga.. it is was lost.
> 2) Because it cannot be seen anymore, it should
> Merlin Moncure wrote:
> > Is there any relatively easy way to, uh, prevent your users from
seeing
> > some/all of your pl/pgsql code in pgAdmin? :) A by schema solution
> > would be ideal.
>
> I could think of an additional option for schema names that should be
> treated as system schema (like
> -Original Message-
> From: Dave Page [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 16, 2005 12:06 PM
> To: Merlin Moncure
> Cc: pgadmin-hackers@postgresql.org
> Subject: RE: [pgadmin-hackers] prevent users from seeing pl/pgsql code
in
> pgadmin
>
>
>
> > -Original Message---
> -Original Message-
> From: Merlin Moncure [mailto:[EMAIL PROTECTED]
> Sent: 16 March 2005 16:54
> To: Dave Page
> Cc: pgadmin-hackers@postgresql.org
> Subject: RE: [pgadmin-hackers] prevent users from seeing
> pl/pgsql code in pgadmin
>
> > > I also tried hacking the search path and
> > I also tried hacking the search path and putting a pg_proc table
into
> > the public schema. While this fixed select * from pg_proc
> > (but not /df),
> > pgAdmin still pulled the function source.
>
> Odd - it didn't here. Every query on pg_proc resulted in a message box
> telling me it couldn
Merlin Moncure wrote:
Is there any relatively easy way to, uh, prevent your users from seeing
some/all of your pl/pgsql code in pgAdmin? :) A by schema solution
would be ideal.
I could think of an additional option for schema names that should be
treated as system schema (like the Slony-I and pgA
> -Original Message-
> From: Merlin Moncure [mailto:[EMAIL PROTECTED]
> Sent: 16 March 2005 16:33
> To: Dave Page
> Cc: pgadmin-hackers@postgresql.org
> Subject: RE: [pgadmin-hackers] prevent users from seeing
> pl/pgsql code in pgadmin
>
>
> I also tried hacking the search path and
> > Is there any relatively easy way to, uh, prevent your users
> > from seeing
> > some/all of your pl/pgsql code in pgAdmin? :) A by schema solution
> > would be ideal.
>
> Anything we did would be fairly pointless given that there's not much
we
> can do to stop them doing 'SELECT prosrc FROM p
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Merlin Moncure
> Sent: 16 March 2005 16:04
> To: pgadmin-hackers@postgresql.org
> Subject: [pgadmin-hackers] prevent users from seeing pl/pgsql
> code in pgadmin
>
> Is there any relatively easy
Is there any relatively easy way to, uh, prevent your users from seeing
some/all of your pl/pgsql code in pgAdmin? :) A by schema solution
would be ideal.
Merlin
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTEC
Log Message:
---
Updated translation from Slawomir Sudnik
Tags:
REL-1_2_0_PATCHES
Modified Files:
--
pgadmin3/src/ui/pl_PL:
pgadmin3.mo (r1.17 -> r1.17.2.1)
pgadmin3.po (r1.18 -> r1.18.2.1)
Index: pgadmin3.po
==
Log Message:
---
Updated translation from Slawomir Sudnik
Modified Files:
--
pgadmin3/src/ui/pl_PL:
pgadmin3.mo (r1.17 -> r1.18)
pgadmin3.po (r1.18 -> r1.19)
Index: pgadmin3.po
===
RCS file: /p
> -Original Message-
> From: Hiroshi Saito [mailto:[EMAIL PROTECTED]
> Sent: 16 March 2005 00:23
> To: Andreas Pflug
> Cc: pgadmin-hackers@postgresql.org; Dave Page
> Subject: Again, the requirement of password of dlgUser.cpp
>
> Hi Andreas.
>
> I have this requirement said by a user
30 matches
Mail list logo
