I concur. I select a database from the Object Explorer in the Default
Workspace, click the "Query Tool" icon and then enter my query. That way,
I bypass the Welcome tab, because the Object Explorer provided all the
necessary context.
So, can I hide the "Welcome" tab of the Query Tool Workspace,
On Thu, 5 Dec 2024 at 04:18, Dave Page wrote:
>
> As of last month, I now work for pgEdge
>
Congratulations, Dave. I hope this chapter is fruitful!
I think there's a nice blend between pagination and infinite scrolling.
The problem with the *current *infinite scrolling implementation is that
the scroll baris scaled to the number of *rendered* rows, so as you scroll
down (which renders another bunch of records), it keeps rescaling the
scrollba
Most browsers also have a "Downloads" item in their main menu (typically
found at the right side of the main toolbar) that'll show you all of the
files you downloaded using the browser.
On Tue, 14 May 2024 at 12:36, Ray O'Donnell wrote:
> On 14/05/2024 16:01, Jarod Steed wrote:
>
> I can’t tell
Please, don't remove the ability to close those system type tabs. The
ability to close them is a small but super improvement.
Agreed, there has to be an obvious way to reopen them, if you want them and
accidentally close them, but I've waited years for the ability to be able
to close them!
Chee
If this is a known issue with a work-around, let me know. Otherwise, I can
log a github issue.
I haven't quite narrowed down the circumstances, but here's roughly the
test case
1. I fire up pgAdmin, and create a bunch of tabs, and stop work at the
end of the day, leaving pgAdmin open.
2
It doesn't even install, which is actually good, because in v6.3 pgAdmin
updated the dependency on python (IIRC) to a version that no longer runs on
Windows 7, whereupon pgAdmin thinks it installed correctly, but you can't
actually use it. So in v6.4, a check was added to prevent pgAdmin from
inst
I'm successfully back to v6.2
Thanks for your help,
Dave
On Fri, Jan 21, 2022 at 8:01 AM Dave Page wrote:
> Hi
>
> On Fri, Jan 21, 2022 at 12:33 PM Dave Caughey wrote:
>
>> I can live with freezing at 6.2.
>>
>> But... it won't run either, because I
x27;m
screwed because the installer moved me from a version that worked to a
version that was known to not run on the OS, with no (apparent) way to get
back to where I was two days ago.
Cheers,
Dave
On Fri, Jan 21, 2022 at 4:27 AM Dave Page wrote:
> Hi
>
> On Thu, Jan 20, 2022 at 7:08 PM D
4.30!
Cheers,
Dave
- previous thread --
On Thu, Feb 25, 2021 at 3:30 PM Dave Page wrote:
>
>
> On Thu, Feb 25, 2021 at 3:13 PM Dave Page wrote:
>
>>
>>
>> On Thu, Feb 25, 2021 at 2:46 PM Dave Caughey wrote:
>>
>>> Here's
I still get the same message after a complete uninstall/reinstall.
I am on Windows 7 SP1
Cheers,
Dave
On Thu, Jan 20, 2022 at 12:04 AM Fahar Abbas
wrote:
> Hi Dave Caughey,
>
> I am not able to reproduce the issue.
>
> How I tested:
>
> 1. Installed pgadmin4 6.2
>
Hi all,
After upgrading from 6.2 to 6.4, when I start pgAdmin I get an
"The pgAdmin 4 server could not be contacted"
message, with the environment details shown below.
I have tried re-installing pgadmin4-6.4-x64.exe, and tried rebooting
windows.
Should I uninstall some component and reinstall?
The UI is indeed a bit confusing...
The explanatory text says "If set to True then data columns will auto-size
to the maximum width of the data in the column as loaded in the first
batch. If False, the column will be sized to the widest of the data type or
column name."
What does "as loaded in th
Rik,
Clearly, if you do
SELECT colA, colB FROM MyTable
vs
SELECT colB, colA FROM MyTable
you'll get the results in a different sequence. Obviously, using this
approach has not manipulated the underlying table (your interpretation of
what the OP is asking for), but perhaps the OP's question is
Hi all,
Normally, there's always been a little pop-up when launching pgAdmin that
says that there's a new version, available.
When I saw the v5.1 release announcement email, I launched pgAdmin v5.0,
saw the new version popup, clicked on it and a new window opened with the
landing page where I wou
With great excitement, I installed the pgAdmin v4.5 on my 64-bit Windows 7
machine, and get the following when I try to launchv4.5.
[image: image.png]
Thankfully v4.30 still runs.
Let me know what logs you'd like/need, and I can create a RM bug.
Cheers,
Dave
On Thu, Feb 25, 2021 at 7:57 AM Ak
On Fri, Feb 5, 2021 at 3:39 PM richard coleman
wrote:
> Dave,
>
> I concur with Alain.
>
> On Fri, Feb 5, 2021 at 3:22 PM Dave Caughey wrote:
>
>> Always naming the file as ".csv", regardless of the delimited used, was a
>> bug that was fixed.
>&g
Always naming the file as ".csv", regardless of the delimited used, was a
bug that was fixed.
The problem with always naming a file as ".csv" is that Excel then blindly
assumes that the file actually does contain comma-delimited fields, and
bypasses the Import From Text Wizard, so if you use anyth
y escape characters in it like - "Sample's" ? If
> yes, then the issue is known and the fix will be available in the next
> release.
>
> On Tue, Feb 2, 2021 at 2:51 AM Dave Caughey wrote:
>
>> Running 4.30, I was busy working with my various databases, and when I
Running 4.30, I was busy working with my various databases, and when I
clicked on one of them, I got a message box with the title "Error
retrieving data from the server: INTERNAL SERVER ERROR" and the body
"String indices must be integers".
I tried closing/reopening the browser client, but not it
In my databases, timestamps are stored as longs (epoch millis).
Consequently, when I do a query or view table, I always end up with values
like 1612106244000, rather than a more readable format of "2021-01-31
15:17:24".
Yes, I realize I can do "to_timestamp(cast(mytimestamp/1000 as
bigint))::time
tutiluren,
I think everyone understands that the usability isn't optimal. Indeed, in
my son's university program, they have a course on UE design, and pgAdmin
is used as a case study of a suboptimal user experience (sorry, don't shoot
me, I'm just the messenger!)
I've logged several feature requ
Check the analytics... I think you'll find dropping it is a non-issue. In
my own web service, I found that IE (all versions) constituted only about
1% of my users.
So I dropped support for IE (since it was preventing me from fully adopting
ES6), and there was not a single complaint from my users.
On Thu, Jan 30, 2020 at 9:21 AM Dave Caughey wrote:
> Hi all,
>
> I'm attempting to back up some databases, but they keep failing after many
> hours with an "exit code: 1".
>
> I've tried format "Plain" and "Tar". I'm using
Hi all,
I'm attempting to back up some databases, but they keep failing after many
hours with an "exit code: 1".
I've tried format "Plain" and "Tar". I'm using UTF8 encoding. I'm
accepting all the default dump options with the exception of additionally
enabling the "Include CREATE DATABASE com
How do we reopen a redmine bug that was rejected? E.g., a bug was
incorrectly marked as a duplicate of another issue.
I see that I can add another comment, but that doesn't change the status...
Cheers,
Dave
Closing and restarting pgAdmin was the only way I could find after
accidentally detaching a pane.
Cheers,
Dave
On Tue, Aug 20, 2019 at 1:52 PM Tony Shelver wrote:
> Accidentally detached the result window in the Query tool, how do i get it
> back again so it's no longer floating?
>
> I have us
That would be pretty easy, as the generated HTML has an "even"/"odd" class.
You can even manually alternating row styles by bringing up the browser's
developer console (F12) and manually adding the following rule to the
applied styles
.ui-widget-content.slick-row.even { background-color: #f8f8f8
In the navigator, drill down to your tables. Right-click on any table, and
select "Count Rows".
A little pale-green popup appears in the lower right corner of pgAdmin that
says "Table Rows Counted". But that's all it says... I.e., it doesn't
actually report the number of rows in that table, as
text items a major
functionality gap? No. But is it a *completely unnecessary* every-day
usability irritant? Yes.
Cheers,
Dave
On Tue, Jul 30, 2019 at 11:52 AM Dave Page wrote:
>
>
> On Tue, Jul 30, 2019 at 4:45 PM Dave Caughey wrote:
>
>> No, it doesn't work. It's
No, it doesn't work. It's logged as #4229. It would be *really* nice if
this were fixed.
Cheers,
Dave
On Tue, Jul 30, 2019 at 10:55 AM Dave Page wrote:
>
>
> On Tue, Jul 30, 2019 at 3:08 PM Mike Martin wrote:
>
>> The only thing I would like to see is the return of copy/paste in query
>> wi
Yes, your fix worked.
Cheers,
Dave
On Thu, Jul 25, 2019 at 10:32 AM Akshay Joshi
wrote:
> Hi Dave
> On Thu, 25 Jul, 2019, 18:59 Dave Caughey, wrote:
>
>> Hi Akshay,
>>
>> There's a bad URL on the release page.
>>
>> The windows URL is missi
Hi Akshay,
There's a bad URL on the release page.
The windows URL is missing the "v" in front of "4.11". It should be
https://www.postgresql.org/ftp/pgadmin/pgadmin4/v4.11/windows/
Cheers,
Dave
On Thu, Jul 25, 2019 at 9:06 AM Akshay Joshi
wrote:
> The pgAdmin Development Team are pleased to
" It's like when you double-click on a file and it opens in an editor -
most will not enable the save button at that point. "
I'm not sure about that claim... pretty much every application I use (MS
Office suite, Adobe suite, vim, notepad, GIMP, etc.) all give you an
enabled Save for any opened d
> 3. At least on CentOS pgadmin 4.8, if I right click my query to copy it,
> instead of the copy option, I just get panel options. Can we please have
> copy/cut there too?
>
Yeah, very annoying. I have already logged that as
https://redmine.postgresql.org/issues/4229
Hi Khushboo,
And then what's the process to upload the downloaded records into the other
database?
Cheers,
Dave
On Mon, Mar 25, 2019 at 12:14 AM Khushboo Vashi <
khushboo.va...@enterprisedb.com> wrote:
>
>
> On Fri, Mar 22, 2019 at 6:06 PM Dave Caughey wrote:
>
A simple write loop inside a read loop and two
> connections usually does the trick.
>
> rik.
>
> On Fri, Mar 22, 2019 at 9:59 AM Dave Caughey wrote:
>
>> Unfortunately, using simple SQL statements isn't an option when dealing
>> with multiple databases (e.g., mov
; mortals...)
>
> Regards
> Calle
>
> On Fri, 22 Mar 2019 at 13:36, Dave Caughey wrote:
>
>> Sorry, for the basic question, but I'm not sure if there are bug(s) in
>> pgAdmin, or just that I'm clueless. (My money lies on the latter!)
>>
>> Imagine t
Sorry, for the basic question, but I'm not sure if there are bug(s) in
pgAdmin, or just that I'm clueless. (My money lies on the latter!)
Imagine the scenario where you are adding a feature to a product that
requires adding some new rows to a configuration table, and as part of the
patch you need
discussed).
>
> On Fri, Mar 15, 2019 at 6:36 PM Dave Caughey wrote:
>
>> I think you're confusing my point.
>>
>> You're right that you never want to add an *implicit* default to the
>> order clause. That would be changing the SQL standard which, as
ui. Absolutely but
> you need to be explicit which one.
>
>
>
> *Doug Easterbrook*
> *Arts Management Systems Ltd.*
> mailto:d...@artsman.com
> http://www.artsman.com
> Phone (403) 650-1978
>
> On Mar 15, 2019, at 8:24 AM, Dave Caughey wrote:
>
> Yeah,
Yeah, but that's just what the spec says about how the SELECT works. It's
not a statement about how a user interface should display information.
Presenting unordered information is basically guaranteed to be never what
the user wants. In this case, the user has to *almost always* edit the
query
Agreed!
On Thu, Aug 9, 2018 at 10:10 AM Rob Richardson
wrote:
> In pgAdmin 3, if I select a table with a few thousand rows and then click
> the Edit button, I get a grid of data and a vertical scrollbar. If I drag
> the scrollbar's thumb to the bottom of the bar, I am taken to the bottom of
> m
And my input on the subject of workflow...
For me, as a developer/maintainer/supporter, my number one points of
interaction are via the Query Tool and the "View/Edit Data | Filtered
Rows", the later of which is *the* most buried bit of functionality.
I realize everyone's needs are slightly differ
When selecting a table in my database, and selecting "View/Edit Data" |
"Filtered Rows...", it would be great if you set the input focus to the
dialog's text area. Having to re-position the mouse, and then click in
the field is and unneeded aggravation.
Cheers,
Dave
Currently, when I launch pgAdmin, it takes 15 clicks to get to the table
I'm interested in. (7 double clicks + 1 selection)
This could be drastically reduced without changing the interface, i.e.,
1. When pgAdmin first opens, there's no reason for the "Servers" item in
the tree to be collapsed. I
46 matches
Mail list logo