Hello,
Using pgAdmin III version 1.14.3, PostgreSQL 9.1.5, Windows 7/64 bit
I've created a Role in a new database called [appuser]. I'd like this user to
be able to run queries and view data in tables, but not be able to alter
anything in the given schema. So I issued the following command:
Thanks, Akshay, confirmed that this is fixed.
I'm also getting an assertion failure after creating a schema. Text:
http://pastebin.com/ifNhBEJq This occurs after clicking OK in the New
Schema dialog and comes up multiple times (seems to be once for every
existing schema + 1). This is not new,
On Tue, Nov 27, 2012 at 5:27 PM, Fernando Hevia wrote:
>
> On Mon, Nov 26, 2012 at 9:55 AM, Andrew Taylor
> wrote:
>> [also posted to Django users Google group]
>>
>> Hi all,
>>
>> Can I bypass the need for password entry in pgadmin3 by
>> changing/locating/permissioning a .pgpass files instead o
On Mon, Nov 26, 2012 at 9:55 AM, Andrew Taylor
wrote:
> [also posted to Django users Google group]
>
> Hi all,
>
> Can I bypass the need for password entry in pgadmin3 by
> changing/locating/permissioning a .pgpass files instead of modifying
> pg_hba.conf to 'trust'? pg_hba.conf currently set at m
