Hi,
I just upgraded to pgAdmin 4 v.1.5 on OS X 10.11.6. I opened a table (view all
rows), and the page up/down buttons don’t work when the query results grid is
in focus.
Also, when the query is refreshed, the columns lose their custom widths. Since
the default widths are very wide for short t
2014-02-26 13:27 GMT+09:00 Ashesh Vashi :
> Done.
> Checked-in in the master and REL-1_18_0_PATCHES branch.
>
>
Many thanks. If someone can provide a Windows build, I can
verify it in the environment where the issue occurred.
Regards
Ian Barwick
>
>
On Wed, Feb 26, 2014 at 9:42 AM, Ashesh Vash
Done.
Checked-in in the master and REL-1_18_0_PATCHES branch.
On Wed, Feb 26, 2014 at 9:42 AM, Ashesh Vashi wrote:
> On Wed, Feb 26, 2014 at 4:28 AM, Ian Lawrence Barwick
> wrote:
>
>> Just wondering - is anything happening with this patch?
>>
> I was waiting for other hackers for their respon
On Wed, Feb 26, 2014 at 4:28 AM, Ian Lawrence Barwick wrote:
> Just wondering - is anything happening with this patch?
>
I was waiting for other hackers for their response.
I will check-in the patch as nobody objected.
Thanks for the reminder though.
>
> Regards
>
> Ian Barwick
>
> 2014-02-05 19
Just wondering - is anything happening with this patch?
Regards
Ian Barwick
2014-02-05 19:02 GMT+09:00 Ian Lawrence Barwick :
> Thanks for the update .
>
> Regards
>
> Ian Barwick
>
>
> 2014-02-05 Ashesh Vashi :
>
> Dave,
>>
>> The patch, sent by Ian Lawrence, looks good me.
>> I also found som
Thanks for the update .
Regards
Ian Barwick
2014-02-05 Ashesh Vashi :
> Dave,
>
> The patch, sent by Ian Lawrence, looks good me.
> I also found some other places, where the similar changes were required
> (specially in debugger code).
> I've attached the combined patch (debugger changes and I
Dave,
The patch, sent by Ian Lawrence, looks good me.
I also found some other places, where the similar changes were required
(specially in debugger code).
I've attached the combined patch (debugger changes and Ian's patch).
If nobody has any objection, I will check-in the patch on both
REL-1_18_
2014/1/10 Ashesh Vashi
> Sorry - it was missed due to busy schedule.
> I will take a look at it.
>
> Thanks for the reminder.
>
No worries, thanks for replying so quickly.
Regards
Ian Barwick
>
>
> On Fri, Jan 10, 2014 at 1:36 PM, Ian Lawrence Barwick
> wrote:
>
>> 2013/11/22 Ian Lawrence B
Sorry - it was missed due to busy schedule.
I will take a look at it.
Thanks for the reminder.
On Fri, Jan 10, 2014 at 1:36 PM, Ian Lawrence Barwick wrote:
> 2013/11/22 Ian Lawrence Barwick :
> > 2013/11/22 Ian Lawrence Barwick :
> >
> >>>
> >>> BTW other objects (tables, schemas etc.) with OID
2013/11/22 Ian Lawrence Barwick :
> 2013/11/22 Ian Lawrence Barwick :
>
>>>
>>> BTW other objects (tables, schemas etc.) with OIDs greater than 256^4/2 - 1
>>> don't seem to be affected by this.
>>
>> It's been a while since I've looked at the pgAdmin source, but some wild
>> grepping shows that in
2013/11/22 Ian Lawrence Barwick :
>>
>> BTW other objects (tables, schemas etc.) with OIDs greater than 256^4/2 - 1
>> don't seem to be affected by this.
>
> It's been a while since I've looked at the pgAdmin source, but some wild
> grepping shows that in:
>
> pgadmin/schema/pgRole.cpp
>
> the r
2013/11/22 Ian Lawrence Barwick :
>
> 2013/11/22 Ashesh Vashi
>>
>> On Fri, Nov 22, 2013 at 12:40 PM, Ian Lawrence Barwick
>> wrote:
>>>
>>> Hi
>>>
>>> On Windows, if a user role's OID exceeds 256^4/2 - 1 (aka 2147483647),
>>> the OID is displayed as 2147483647 and additional information for that
2013/11/22 Ashesh Vashi
> On Fri, Nov 22, 2013 at 12:40 PM, Ian Lawrence Barwick
> wrote:
>
>> Hi
>>
>> On Windows, if a user role's OID exceeds 256^4/2 - 1 (aka 2147483647),
>> the OID is displayed as 2147483647 and additional information for that
>> object
>> (e.g. ACL information) is not disp
On Fri, Nov 22, 2013 at 12:40 PM, Ian Lawrence Barwick wrote:
> Hi
>
> On Windows, if a user role's OID exceeds 256^4/2 - 1 (aka 2147483647),
> the OID is displayed as 2147483647 and additional information for that
> object
> (e.g. ACL information) is not displayed.
>
> We have verified this happe
Hi
On Windows, if a user role's OID exceeds 256^4/2 - 1 (aka 2147483647),
the OID is displayed as 2147483647 and additional information for that object
(e.g. ACL information) is not displayed.
We have verified this happens with pgAdmin3 1.16.0 on Windows 7 and
1.18.1 on Windows 2012 server. It do
Hi,
On Thu, 2012-11-15 at 14:39 +, Dave Page wrote:
>
> Please try 1.16.0. 1.14.0 is quite old, and there have been tons of
> bug fixes since that minor version, as well as the major increment
> since then.
Hmm, I just noticed that I pushed 1.16 to f17 already. Let me ask him to
update. Th
Hi
Please try 1.16.0. 1.14.0 is quite old, and there have been tons of
bug fixes since that minor version, as well as the major increment
since then.
On Thu, Nov 15, 2012 at 2:36 PM, Devrim GÜNDÜZ wrote:
>
> Hi,
>
> This was just reported, regarding a SIGSEGV:
>
> https://bugzilla.redhat.com/sho
Hi,
This was just reported, regarding a SIGSEGV:
https://bugzilla.redhat.com/show_bug.cgi?id=877011
Can someone please look at the backtrace given there?
Thanks!
Regards,
--
Devrim GÜNDÜZ
Principal Systems Engineer @ EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant,
2009/12/1 Devrim GÜNDÜZ :
> On Mon, 2009-11-30 at 15:00 +, Dave Page wrote:
>>
>> With no description (that I can see) of what the user was doing
>> exactly, it's hard to suggest anything.
>
> For the records, here is what user did:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=542553#c4
>
>
On Mon, 2009-11-30 at 15:00 +, Dave Page wrote:
>
> With no description (that I can see) of what the user was doing
> exactly, it's hard to suggest anything.
For the records, here is what user did:
https://bugzilla.redhat.com/show_bug.cgi?id=542553#c4
Another bug report was just filed:
htt
2009/11/30 Devrim GÜNDÜZ :
> Hi,
>
> This was filed today against Fedora 12:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=542553
With no description (that I can see) of what the user was doing
exactly, it's hard to suggest anything. For example I fixed a bug a
couple of days ago that might have
Hi,
This was filed today against Fedora 12:
https://bugzilla.redhat.com/show_bug.cgi?id=542553
Regards,
--
Devrim GÜNDÜZ, RHCE
Command Prompt - http://www.CommandPrompt.com
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org Twitter: http://twitter.com/d
On Sat, Nov 15, 2008 at 6:39 AM, Quan Zongliang <[EMAIL PROTECTED]> wrote:
>
> Attachment is the most important debug info. I forgot it.
>
> From it, I know how to modify source.
Ahh, I got it. The bug doesn't occur unless you manually specify the
primary key value (which I normally leave up to th
>
> That seems to work fine in the editor on PG 8.3.4 (really must upgrade
> that!) using pgAdmin 1.8.4 and SVN trunk on OS X. What server version
> and OS are you using? Can anyone else reproduce this?
I tested it in CentOS 5.2 and Windows XP, both got error.
The attachment is snapshot in KDE.
On Fri, Nov 14, 2008 at 10:37 AM, Quan Zongliang
<[EMAIL PROTECTED]> wrote:
>
>>
>> Thanks... but, now I come to test it, I cannot reproduce the problem.
>> Were you testing with SVN trunk, or a release version of pgAdmin?
>
> I had tested at release 1.8.4 and 1.9.0-dev.
> The target column is null
>
> Thanks... but, now I come to test it, I cannot reproduce the problem.
> Were you testing with SVN trunk, or a release version of pgAdmin?
I had tested at release 1.8.4 and 1.9.0-dev.
The target column is nullable, input some value in other columns and
press Enter key. The error will be throw
On Thu, Nov 13, 2008 at 11:01 AM, Quan Zongliang
<[EMAIL PROTECTED]> wrote:
>>
>> Are you in a position to fix it? Your last patch was good, and we
>> always welcome new hackers :-)
>
> Ok, fixed.
Thanks... but, now I come to test it, I cannot reproduce the problem.
Were you testing with SVN trunk
>
> Are you in a position to fix it? Your last patch was good, and we
> always welcome new hackers :-)
Ok, fixed.
---
Quan Zongliang
[EMAIL PROTECTED]
CIT Japan: http://www.cit.co.jp
pgSet_7497.patch
Description: Binary data
--
Sent via pgadmin-ha
On Thu, Nov 13, 2008 at 2:13 AM, Quan Zongliang <[EMAIL PROTECTED]> wrote:
> Sorry, my mistake.
>
> This error is caused by double quotation mark, not comma.
Are you in a position to fix it? Your last patch was good, and we
always welcome new hackers :-)
--
Dave Page
EnterpriseDB UK: http://ww
Sorry, my mistake.
This error is caused by double quotation mark, not comma.
> When column name has commas, using the data grid to insert row will
> causes error.
> For test, I defined column named "quoted col ,""' name".
> A printscreen in attachment.
--
hi
When column name has commas, using the data grid to insert row will
causes error.
For test, I defined column named "quoted col ,""' name".
A printscreen in attachment.
By the way:
I had implemented TODO Item:
- Add support for DESC/NULLS FIRST/NULLS LAST when creating indexes.
It seems work
Zongliang, Quan wrote:
> In pgServer.cpp, Line 752:
>
> if (executed)
> {
> password = newVal;
> StorePassword();
> --->return false;
> }
> else
> return false;
>
> Although the passwd had been changed successfully with "Change Password"
> dialog. "The
In pgServer.cpp, Line 752:
if (executed)
{
password = newVal;
StorePassword();
--->return false;
}
else
return false;
Although the passwd had been changed successfully with "Change Password"
dialog. "The password could not be changed!" message always po
Quan Zongliang wrote:
> Thanks, It's OK.
Great :-)
> Now, in tips.txt:
> The answer to the question of Life, the Universe and Everything is 42.
> This statement is too difficult to translate it.
> What's meaning ?
> Help me, please.
:-) It's a joke entry - leave it out if it doesn't make s
> --- Original Message ---
> From: Quan Zongliang <[EMAIL PROTECTED]>
> To: Dave Page <[EMAIL PROTECTED]>
> Sent: 21/03/07, 13:11:30
> Subject: Re: [pgadmin-hackers] bug report about tips
>
> Now it is GB2312
>
> How to convert it?
I believe th
Now it is GB2312
How to convert it?
--
权 宗亮(Quan Zongliang)
[EMAIL PROTECTED],[EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so
Quan Zongliang wrote:
> Encoding is zh_CN.
Thats a language, not an encoding. The encoding might be UTF-8, Ascii,
EUC_CN etc.
Regards, Dave
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgre
Encoding is zh_CN.
--
权 宗亮(Quan Zongliang)
[EMAIL PROTECTED],[EMAIL PROTECTED]
tips.txt
Description: Binary data
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org
Quan Zongliang wrote:
hi!
I am translating tips.txt to Chinese-simplified.
It seems in frmHint.cpp has a bug.
When read multibyte tips file, always display "Failed to convert file ... to
Unicode".
It is throwed at line 135 in wxWidgets\src\common\textfile.cpp.
After line 129: const wxString s
hi!
I am translating tips.txt to Chinese-simplified.
It seems in frmHint.cpp has a bug.
When read multibyte tips file, always display "Failed to convert file ... to
Unicode".
It is throwed at line 135 in wxWidgets\src\common\textfile.cpp.
After line 129: const wxString str(buf, conv, bufPos); i
40 matches
Mail list logo
