On Tue, Aug 2, 2016 at 9:08 AM, Kieran McCusker
<kieran.mccusker@kwest.info> wrote:
> Hi
>
> Just been looking at the SQL editor in pgAdmin4. Issues I see at the moment
> are:
>
> My users spend a lot of their day editing scripts that are held on the
> network.
> It looks currently like you have to map each network drive to a drive letter
> (in windows).
Yes, UNC paths are not directly supported at present.
> It takes 3-4 seconds from clicking the Open File button to the file selector
> being shown.
> In pgAdmin 1.22 it is instant.
pgAdmin 4 is naturally going to be slower as it's a web app, whereas
pgAdmin III was a native app. That said, it's instant on my machine.
Can you run in full web mode and get any clues from the console as to
what request is slow exactly?
> The editor has no search / search and replace and no configuration options
> (tabs vs spaces number of spaces per indent etc).
> The scripts my users have are pulling in data and cleaning it. They tend to
> be quite long.
No, not yet - unfortunately there was only so much we could get in the
first version. Patches are welcome.
> There doesn't appear to be a shortcut for executing the SQL (used to be F5)
The shortcuts are shown on the menu/tooltips. From the next beta, F5
will work again, overriding whatever your browser uses F5 for, but
only when the query tool's SQL text box has focus (the current
shortcuts work all the time, but so many people wanted F5 back, that
we've had to make that compromise).
> I appreciate this is still beta, but thought it worth mentioning these
> issues as they will cause problems for my users.
>
> Thanks
>
> Kieran
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
