Hi Richard,
Thanks for your response. I have been able to solve the mystery. The
problem was from QGIS as suspected. When you create the first user
connection to the database (PostgreSQL/PostGIS in this case) and you add a
new connection with a different user or edit the first connection to a
diff
Hi Richard,
Thanks for your response. I have been able to solve the mystery. The
problem was from QGIS as suspected. When you create the first user
connection to the database (PostgreSQL/PostGIS in this case) and you add a
new connection with a different user or edit the first connection to a
diff
I can not reproduce your issue. I have a standard read-only user. I connect
from qgis to postgres with that user and I can not even enable editing in
qgis (the "pencil" button is disabled). I'm on Linux, postgres 9.4, qgis
2.14. It sounds like your pgadmin is working as expected so I would suggest
Hi Tim,
Ok, thanks for your help.
On Fri, Mar 17, 2017 at 4:32 PM, HEARNE, TIMOTHY S wrote:
> I am unfamiliar with the QGIS product. If when you logon using pgAdmin,
> you can’t change the field / column then it is probably not a configuration
> issue on the database side.
>
> It may be relate
I am unfamiliar with the QGIS product. If when you logon using pgAdmin, you
can’t change the field / column then it is probably not a configuration issue
on the database side.
It may be related to how the QGIS tool is configured and the permissions
necessary to use the tool. You may want to re
I would like to know why the privileges/permission is working when tested
with pgAdmin/pgsql, but it is not working with the same user/schema/table
in QGIS.
-- Forwarded message --
From: Osahon Oduware
Date: Fri, Mar 17, 2017 at 4:17 PM
Subject: Re: [pgadmin-support] QGIS Seem To
I can confirm that the user is not a superuser. This is the script
generated for the user:
CREATE USER WITH LOGIN NOSUPERUSER INHERIT NOCREATEDB
NOCREATEROLE NOREPLICATION;
GRANT TO ;
**Where is as created in previous mail
On Fri, Mar 17, 2017 at 4:08 PM, HEARNE, TIMOTHY S wrote:
> If you
The role was created as shown below:
CREATE ROLE WITH NOLOGIN NOSUPERUSER INHERIT NOCREATEDB
NOCREATEROLE NOREPLICATION;
On Fri, Mar 17, 2017 at 3:56 PM, HEARNE, TIMOTHY S wrote:
> Did you create the user with SUPERUSER or some other elevated privilege?
> Since you did not include the script f
Hi,
Thanks for your prompt response. The user was created with the postgres
user (superuser) as below:
CREATE USER WITH PASSWORD ''
Did you create the user with SUPERUSER or some other elevated privilege? Since
you did not include the script for the user, it is hard to determine the exact
root cause.
If you have any questions, please feel free to contact me.
Tim Hearne
CAST / Flex Force Application DBA
Principal DBA
Centrali
Hi All,
I created a "Read-only" User in PostgreSQL via a Role with "SELECT" ONLY
privilege on all tables in a schema as shown below:
GRANT SELECT ON ALL TABLES IN SCHEMA [schema_name] TO [role_name]
GRANT [role_name] TO [user_name]
Next, I test this by trying to UPDATE a column in a table (same
On Fri, Mar 17, 2017 at 3:31 AM, Devrim Gündüz wrote:
>
> Hi,
>
> On Thu, 2017-03-16 at 11:55 -0700, Scott Classen wrote:
>> but it is unclear to me where the config_local.py file is supposed to go.
>
> We don't distribute it with the packages, but it should go under here:
>
> /usr/lib/python2.7/s
12 matches
Mail list logo
