Обсуждение: pre-populate pgadmin4 configuration (server, for example)

Поиск
Список
Период
Сортировка

pre-populate pgadmin4 configuration (server, for example)

От
"Duffey, Blake"
Дата:

pgAdmin 3 leveraged registry keys that could be used to ‘pre-populate’ certain connection entries (server, port, SSL, etc) for use cases such as terminal server/Citrix environments.  In our (admittedly limited) testing pgAdmin 4 ver 2 offers no such keys to store connection specific information.  We are looking to switch from 3 to 4 and are hoping to ‘pre-populate’ certain connection options to ease the user burden.

 

Thanks in advance.
Blake 

Re: pre-populate pgadmin4 configuration (server, for example)

От
Murtuza Zabuawala
Дата:
On Wed, Dec 13, 2017 at 3:04 AM, Duffey, Blake <Blake.Duffey@noblis.org> wrote:

pgAdmin 3 leveraged registry keys that could be used to ‘pre-populate’ certain connection entries (server, port, SSL, etc) for use cases such as terminal server/Citrix environments.  In our (admittedly limited) testing pgAdmin 4 ver 2 offers no such keys to store connection specific information.  We are looking to switch from 3 to 4 and are hoping to ‘pre-populate’ certain connection options to ease the user burden.


By default, pgAdmin4 will automatically pre-populate the Postgres servers which are installed locally but user has to add remote Postgres servers manually in server list. 

 

Thanks in advance.
Blake 


RE: pre-populate pgadmin4 configuration (server, for example)

От
"Duffey, Blake"
Дата:

Is there any way to create a custom .db file in the users AppData folder that could simulate what the registry keys did in the version 3?

 

 

 

From: Murtuza Zabuawala [mailto:murtuza.zabuawala@enterprisedb.com]
Sent: Tuesday, December 12, 2017 11:55 PM
To: Duffey, Blake <Blake.Duffey@noblis.org>
Cc: pgadmin-support@lists.postgresql.org
Subject: Re: pre-populate pgadmin4 configuration (server, for example)

 

On Wed, Dec 13, 2017 at 3:04 AM, Duffey, Blake <Blake.Duffey@noblis.org> wrote:

pgAdmin 3 leveraged registry keys that could be used to ‘pre-populate’ certain connection entries (server, port, SSL, etc) for use cases such as terminal server/Citrix environments.  In our (admittedly limited) testing pgAdmin 4 ver 2 offers no such keys to store connection specific information.  We are looking to switch from 3 to 4 and are hoping to ‘pre-populate’ certain connection options to ease the user burden.

 

By default, pgAdmin4 will automatically pre-populate the Postgres servers which are installed locally but user has to add remote Postgres servers manually in server list. 

 

Thanks in advance.
Blake 

 

Re: pre-populate pgadmin4 configuration (server, for example)

От
Dave Page
Дата:


On Wed, Dec 13, 2017 at 1:16 PM, Duffey, Blake <Blake.Duffey@noblis.org> wrote:

Is there any way to create a custom .db file in the users AppData folder that could simulate what the registry keys did in the version 3?


Right now the only option would be to take a freshly created file, and use the sqlite client to execute the appropriate SQL inserts on it to add the servers.

I have been toying with the idea of writing a small command-line tool (and maybe UI tool?) that would let you import and export server definitions, but haven't got round to it yet.
 

 

 

 

From: Murtuza Zabuawala [mailto:murtuza.zabuawala@enterprisedb.com]
Sent: Tuesday, December 12, 2017 11:55 PM
To: Duffey, Blake <Blake.Duffey@noblis.org>
Cc: pgadmin-support@lists.postgresql.org
Subject: Re: pre-populate pgadmin4 configuration (server, for example)

 

On Wed, Dec 13, 2017 at 3:04 AM, Duffey, Blake <Blake.Duffey@noblis.org> wrote:

pgAdmin 3 leveraged registry keys that could be used to ‘pre-populate’ certain connection entries (server, port, SSL, etc) for use cases such as terminal server/Citrix environments.  In our (admittedly limited) testing pgAdmin 4 ver 2 offers no such keys to store connection specific information.  We are looking to switch from 3 to 4 and are hoping to ‘pre-populate’ certain connection options to ease the user burden.

 

By default, pgAdmin4 will automatically pre-populate the Postgres servers which are installed locally but user has to add remote Postgres servers manually in server list. 

 

Thanks in advance.
Blake 

 




--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

RE: pre-populate pgadmin4 configuration (server, for example)

От
"Duffey, Blake"
Дата:

We’d be happy to try that Dave (assuming someone could give us a couple sentences on how to do so)

 

J

 

From: Dave Page [mailto:dpage@pgadmin.org]
Sent: Wednesday, December 13, 2017 8:31 AM
To: Duffey, Blake <Blake.Duffey@noblis.org>
Cc: Murtuza Zabuawala <murtuza.zabuawala@enterprisedb.com>; pgadmin-support@lists.postgresql.org
Subject: Re: pre-populate pgadmin4 configuration (server, for example)

 

 

 

On Wed, Dec 13, 2017 at 1:16 PM, Duffey, Blake <Blake.Duffey@noblis.org> wrote:

Is there any way to create a custom .db file in the users AppData folder that could simulate what the registry keys did in the version 3?

 

Right now the only option would be to take a freshly created file, and use the sqlite client to execute the appropriate SQL inserts on it to add the servers.

 

I have been toying with the idea of writing a small command-line tool (and maybe UI tool?) that would let you import and export server definitions, but haven't got round to it yet.

 

 

 

 

From: Murtuza Zabuawala [mailto:murtuza.zabuawala@enterprisedb.com]
Sent: Tuesday, December 12, 2017 11:55 PM
To: Duffey, Blake <Blake.Duffey@noblis.org>
Cc: pgadmin-support@lists.postgresql.org
Subject: Re: pre-populate pgadmin4 configuration (server, for example)

 

On Wed, Dec 13, 2017 at 3:04 AM, Duffey, Blake <Blake.Duffey@noblis.org> wrote:

pgAdmin 3 leveraged registry keys that could be used to ‘pre-populate’ certain connection entries (server, port, SSL, etc) for use cases such as terminal server/Citrix environments.  In our (admittedly limited) testing pgAdmin 4 ver 2 offers no such keys to store connection specific information.  We are looking to switch from 3 to 4 and are hoping to ‘pre-populate’ certain connection options to ease the user burden.

 

By default, pgAdmin4 will automatically pre-populate the Postgres servers which are installed locally but user has to add remote Postgres servers manually in server list. 

 

Thanks in advance.
Blake 

 



 

--

Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Re: pre-populate pgadmin4 configuration (server, for example)

От
Stephen Frost
Дата:
Hi Blake!

Documentation on the sqlite command line tool can be found here:

https://sqlite.org/cli.html

From there, things like '.help' are useful and you can use it to look at
the schema for tables like 'servers':

.schema servers
.schema servergroup

And from there it's a matter of crafting INSERT commands, information
about which is available here:

https://sqlite.org/lang_insert.html

A certain Brian over there should be able to manage to figure this all
out, if he's not forgotten how... ;)

Thanks!

Stephen

* Duffey, Blake (Blake.Duffey@noblis.org) wrote:
> We’d be happy to try that Dave (assuming someone could give us a couple sentences on how to do so)
>
> ☺
>
> From: Dave Page [mailto:dpage@pgadmin.org]
> Sent: Wednesday, December 13, 2017 8:31 AM
> To: Duffey, Blake <Blake.Duffey@noblis.org>
> Cc: Murtuza Zabuawala <murtuza.zabuawala@enterprisedb.com>; pgadmin-support@lists.postgresql.org
> Subject: Re: pre-populate pgadmin4 configuration (server, for example)
>
>
>
> On Wed, Dec 13, 2017 at 1:16 PM, Duffey, Blake <Blake.Duffey@noblis.org<mailto:Blake.Duffey@noblis.org>> wrote:
> Is there any way to create a custom .db file in the users AppData folder that could simulate what the registry keys
didin the version 3? 
>
> Right now the only option would be to take a freshly created file, and use the sqlite client to execute the
appropriateSQL inserts on it to add the servers. 
>
> I have been toying with the idea of writing a small command-line tool (and maybe UI tool?) that would let you import
andexport server definitions, but haven't got round to it yet. 
>
>
>
>
> From: Murtuza Zabuawala [mailto:murtuza.zabuawala@enterprisedb.com<mailto:murtuza.zabuawala@enterprisedb.com>]
> Sent: Tuesday, December 12, 2017 11:55 PM
> To: Duffey, Blake <Blake.Duffey@noblis.org<mailto:Blake.Duffey@noblis.org>>
> Cc: pgadmin-support@lists.postgresql.org<mailto:pgadmin-support@lists.postgresql.org>
> Subject: Re: pre-populate pgadmin4 configuration (server, for example)
>
> On Wed, Dec 13, 2017 at 3:04 AM, Duffey, Blake <Blake.Duffey@noblis.org<mailto:Blake.Duffey@noblis.org>> wrote:
>
> pgAdmin 3 leveraged registry keys that could be used to ‘pre-populate’ certain connection entries (server, port, SSL,
etc)for use cases such as terminal server/Citrix environments.  In our (admittedly limited) testing pgAdmin 4 ver 2
offersno such keys to store connection specific information.  We are looking to switch from 3 to 4 and are hoping to
‘pre-populate’certain connection options to ease the user burden. 
>
> By default, pgAdmin4 will automatically pre-populate the Postgres servers which are installed locally but user has to
addremote Postgres servers manually in server list. 
>
>
>
> Thanks in advance.
> Blake
>
>
>
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company

Вложения