+1
Cheers
On 6 September 2020 19:18:26 CEST, "Régis Haubourg"
wrote:
>Hi,
>I'm my opinion, we should add a dialog to let the user choose the
>destination schema. Public schema should really be left untouched by
>default.
>Cheers
>Regis
>
>Le dim. 6 sept. 2020 à 18:26, Giovanni Manghi
> a
>écrit
Hi,
I'm my opinion, we should add a dialog to let the user choose the
destination schema. Public schema should really be left untouched by
default.
Cheers
Regis
Le dim. 6 sept. 2020 à 18:26, Giovanni Manghi a
écrit :
> Hi all,
>
> On Sat, Sep 5, 2020 at 11:05 PM Paolo Cavallini
> wrote:
> >
> >
Hi all,
On Sat, Sep 5, 2020 at 11:05 PM Paolo Cavallini wrote:
>
> This follows the search_path setting.
oh I see. Anyway this case seems possible (even if uncommon), and when
it happens it leads a user to being cut off from accessing styles
stored in public.
So my question stands, should this b
This follows the search_path setting.
Cheers.
On 5 September 2020 23:38:03 CEST, Giovanni Manghi
wrote:
>Hi all,
>by chance I noticed the following:
>
>If in a PostgreSQL DB exists a schema that has the same name as a user
>that has full permissions on that schema, then if the user saves a
>styl
Hi all,
by chance I noticed the following:
If in a PostgreSQL DB exists a schema that has the same name as a user
that has full permissions on that schema, then if the user saves a
style to the DB this is saved in a "layer_styles" table in this
schema, not public.
Moreover if the user tries to l
