I put a build at
https://developer.pgadmin.org/~dpage/pgadmin4-1.1-x86.exe. There's a
Mac build there as well for anyone that wants it:
https://developer.pgadmin.org/~dpage/pgadmin4-1.1.dmg
Both are *completely untested*.
On Mon, Dec 5, 2016 at 2:12 AM, Dave Page wrote:
> Oh sorry - I forgot the
Oh sorry - I forgot there's a change in the required dependencies for Python
(so you should roll back your changes). When I'm back in the office tomorrow,
I'll see if I can roll you a custom build. Please remind me if I forget!
Thanks.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @p
Am 03.12.2016 um 05:06 schrieb Dave Page:
On Sat, Dec 3, 2016 at 2:44 AM, Andreas wrote:
Am 03.12.2016 um 03:13 schrieb Dave Page:
Where can I get the 1.2?
An editor without search&replace is a wee bit suboptimal.
It's not out yet, but you can get the code from the GIT repo
(https://git.po
On Sat, Dec 3, 2016 at 2:44 AM, Andreas wrote:
> Am 03.12.2016 um 03:13 schrieb Dave Page:
>>
>> On Sat, Dec 3, 2016 at 1:41 AM, Andreas wrote:
>>>
>>> Am 03.12.2016 um 02:00 schrieb Dave Page:
On Sat, Dec 3, 2016 at 12:35 AM, Andreas wrote:
>
>
>>> yes, but there is this V1.23 LTS of
Am 03.12.2016 um 03:13 schrieb Dave Page:
On Sat, Dec 3, 2016 at 1:41 AM, Andreas wrote:
Am 03.12.2016 um 02:00 schrieb Dave Page:
On Sat, Dec 3, 2016 at 12:35 AM, Andreas wrote:
yes, but there is this V1.23 LTS of BigSQL.
That is nothing to do with us.
Their Installer is on the Postgre
On Sat, Dec 3, 2016 at 1:41 AM, Andreas wrote:
> Am 03.12.2016 um 02:00 schrieb Dave Page:
>> On Sat, Dec 3, 2016 at 12:35 AM, Andreas wrote:
>>> Hi,
>>> there appears to be a bug in bug in pgAdmin 3 1.23.0a LTS when I
>>> Drag&Drop a script into
Am 03.12.2016 um 02:00 schrieb Dave Page:
> On Sat, Dec 3, 2016 at 12:35 AM, Andreas wrote:
>> Hi,
>> there appears to be a bug in bug in pgAdmin 3 1.23.0a LTS when I
>> Drag&Drop a script into the editor.
>
> pgAdmin 3 is no longer supported I'm afraid.
On Sat, Dec 3, 2016 at 12:35 AM, Andreas wrote:
> Hi,
> there appears to be a bug in bug in pgAdmin 3 1.23.0a LTS when I
> Drag&Drop a script into the editor.
pgAdmin 3 is no longer supported I'm afraid.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
Ent
Hi,
there appears to be a bug in bug in pgAdmin 3 1.23.0a LTS when I
Drag&Drop a script into the editor.
The script is read in fine but the editor doesn't remember the name of
the file. So when I want to save the changes, I need to select the
allready existing file and get asked
I'm using pgAdmin 1.16.1 on Windows and am seeing this curious behavior:
I'm connected to postgresql 9.2.4.
When creating a database, I click on the owner combo-box, and see what appears
to be a composite list of available roles, then users.
I choose one of the users, who happens to have a name
Le 25/03/2011 09:28, Dan S a écrit :
> Thanks !
> That will be nice to have !
>
> Do you think the new release of pgAdmin will be ready and packaged when
> postgres 9.1 will be released ?
>
That's what we usually do, yes.
--
Guillaume
http://www.postgresql.fr
http://dalibo.com
--
Sent vi
Thanks !
That will be nice to have !
Do you think the new release of pgAdmin will be ready and packaged when
postgres 9.1 will be released ?
Best Regards
Dan
2011/3/24 Guillaume Lelarge
> Le 13/03/2011 10:54, Guillaume Lelarge a écrit :
> > Le 13/03/2011 10:35, Dan S a écrit :
> >> Hi !
> >>
Le 13/03/2011 10:54, Guillaume Lelarge a écrit :
> Le 13/03/2011 10:35, Dan S a écrit :
>> Hi !
>>
>> I'm running pgadmin v. 1.12.2 on winxp and postgres "PostgreSQL 9.0.2,
>> compiled by Visual C++ build 1500, 32-bit".
>>
>> When selecting a table in the tree-navigator to the left the table
>> def
Le 13/03/2011 10:35, Dan S a écrit :
> Hi !
>
> I'm running pgadmin v. 1.12.2 on winxp and postgres "PostgreSQL 9.0.2,
> compiled by Visual C++ build 1500, 32-bit".
>
> When selecting a table in the tree-navigator to the left the table
> definition and its triggers appears to the right.
> However
Hi !
I'm running pgadmin v. 1.12.2 on winxp and postgres "PostgreSQL 9.0.2,
compiled by Visual C++ build 1500, 32-bit".
When selecting a table in the tree-navigator to the left the table
definition and its triggers appears to the right.
However the trigger definition doesn't appear to be right (
On 03/06/2009 00:15, Marek wrote:
>> On 02/06/2009 09:45, Marek wrote:
>>> I have fund bug in query editor. Very often it is not possible to paste
> text
>>> from clipboard. Option "edit/paste" is grayed, shortcut Ctrl+V doesn't
> work
>>> as well. When query editor is prefilled with SQL of selecte
On 02/06/2009 09:45, Marek wrote:
> I have fund bug in query editor. Very often it is not possible to paste text
> from clipboard. Option "edit/paste" is grayed, shortcut Ctrl+V doesn't work
> as well. When query editor is prefilled with SQL of selected object (eg.
I think this has been fixed for
Hello,
I have fund bug in query editor. Very often it is not possible to paste text
from clipboard. Option "edit/paste" is grayed, shortcut Ctrl+V doesn't work
as well. When query editor is prefilled with SQL of selected object (eg.
database name) then removing of window contents unlocks pastin
On Feb 15, 2008 11:00 PM, Peter Gagarinov <[EMAIL PROTECTED]> wrote:
> CREATE TABLE derived_table
> (
> -- Inherited: a integer,
> -- Inherited: b integer,
> c integer,
> -- Inherited: d integer
> )
> INHERITS (basic_table, basic_table_b)
> WITH (OIDS=FALSE);
> ALTER TABLE derived_table OW
Prerequisites:
pgAdmin 1.8.2, Windows Xp SP2, Postgres 8.3.0
Steps to reproduce:
1)Run the following sequence.
create table basic_table(
a integer,
b integer);
create table derived_table(
c integer
) inherits (basic_table);
create table basic_table_b
(d integer);
alter table derived_table
On Feb 13, 2008 3:06 PM, Guillaume Lelarge <[EMAIL PROTECTED]> wrote:
> What do you think of the UI I mention in my previous mail ? if it feels
> OK to you (and others), I'll have a look at it.
Probably best to hold off for now - redesigning the table & child
dialogues is on the todo for this cycl
Dave Page a écrit :
On Feb 13, 2008 2:56 PM, Guillaume Lelarge <[EMAIL PROTECTED]> wrote:
That's something I already heard at Solutions Linux 2008. I talked with
someone who has this kind of issues. This guy has lots of tables, so his
type combo box is really huge, and becomes actually unusable.
Dave Page wrote:
On Feb 13, 2008 2:56 PM, Guillaume Lelarge <[EMAIL PROTECTED]> wrote:
That's something I already heard at Solutions Linux 2008. I talked with
someone who has this kind of issues. This guy has lots of tables, so his
type combo box is really huge, and becomes actually unusable.
T
On Feb 13, 2008 2:56 PM, Guillaume Lelarge <[EMAIL PROTECTED]> wrote:
> That's something I already heard at Solutions Linux 2008. I talked with
> someone who has this kind of issues. This guy has lots of tables, so his
> type combo box is really huge, and becomes actually unusable.
>
> Table types
Magnus Hagander a écrit :
Dave Page wrote:
On Feb 12, 2008 9:12 PM, Peter Gagarinov <[EMAIL PROTECTED]> wrote:
1) create a simple table with two columns :
create test_table(a integer, b integer);
2) go to 'New Table.." menu, type in some table name,
3) go to 'Columns' tab, typ
Dave Page wrote:
On Feb 12, 2008 9:12 PM, Peter Gagarinov <[EMAIL PROTECTED]> wrote:
1) create a simple table with two columns :
create test_table(a integer, b integer);
2) go to 'New Table.." menu, type in some table name,
3) go to 'Columns' tab, type some column name, 'a' for
On Feb 12, 2008 9:12 PM, Peter Gagarinov <[EMAIL PROTECTED]> wrote:
>
> 1) create a simple table with two columns :
>
> create test_table(a integer, b integer);
>
> 2) go to 'New Table.." menu, type in some table name,
>
> 3) go to 'Columns' tab, type some column name, 'a' for instan
Prerequisites:
Binary downloaded from website, used along with Postgres 8.3.0
Windows XP Pro, SP2
Steps to reproduce
1) create a simple table with two columns :
create test_table(a integer, b integer);
2) go to ‘New Table..” menu, type in some table name,
3) go to ‘Columns’ ta
Kieran McCusker wrote:
Another report - Sorry I haven't had time to check if it has already
been reported.
Create a new table without a primary key (I did it using the SQL pane.)
my example is:-
CREATE TABLE t
(
id integer,
t text
)
Do the following :-
1. Right click on the table in the
Another report - Sorry I haven't had time to check if it has already
been reported.
Create a new table without a primary key (I did it using the SQL pane.)
my example is:-
CREATE TABLE t
(
id integer,
t text
)
Do the following :-
1. Right click on the table in the properties pane and sel
Kieran McCusker wrote:
> This bug has been around a while, sorry its taken me so long to report it.
>
> In the sql editor do the following :-
> 1. Open Find and replace
> 2. Check regular expressions
> 3. In Find what enter $
> 4. In Replace with enter anything
> 5. Click Replace All
>
> pgadmin
This bug has been around a while, sorry its taken me so long to report it.
In the sql editor do the following :-
1. Open Find and replace
2. Check regular expressions
3. In Find what enter $
4. In Replace with enter anything
5. Click Replace All
pgadmin seems to go into a loop where pgadmin stop
Hi,
- i set the preference "Read and write Unicode UTF-8 files" to true.
It does not have any effet on the program behaviour anyway.
- the operating system variables LANG and LC_* are all already set to
"en_US.UTF-8".
What shall i change more? vi shows the german characters well!
Dave Page
Guillaume Lelarge wrote:
> Hi,
>
> Andreas Kutschke a écrit :
>> on Linux i cannot open the attached SQL-File in the "PgAdmin III Query".
>> On Windows (XP) there are no problems.
>> I choose the directory (nfs-mounted) and then the file. On "open" the
>> file selection box closes, but nothing hap
Hi,
Andreas Kutschke a écrit :
> on Linux i cannot open the attached SQL-File in the "PgAdmin III Query".
> On Windows (XP) there are no problems.
> I choose the directory (nfs-mounted) and then the file. On "open" the
> file selection box closes, but nothing happens.
> Other sql-Files from the sa
Hi,
on Linux i cannot open the attached SQL-File in the "PgAdmin III Query".
On Windows (XP) there are no problems.
I choose the directory (nfs-mounted) and then the file. On "open" the file
selection box closes, but nothing happens.
Other sql-Files from the same directory can be opened! The fil
yychen a écrit :
> SERVER running postgresql on
> port 5432 for ver 7.1.14
> port 5439 for ver 8.2.0
>
> While PgAdmin 1.6.1 connecting to SERVER:5439 !
> Success connection ..but
> (1) show pg version is 7.1.14
> (2) show no database in it!
>
It works for me. I tried with
port 5432 wi
SERVER running postgresql on
port 5432 for ver 7.1.14
port 5439 for ver 8.2.0
While PgAdmin 1.6.1 connecting to SERVER:5439 !
Success connection ..but
(1) show pg version is 7.1.14
(2) show no database in it!
Patrick Headley wrote:
PGAdmin III v1.6.1 binary install
Windows XP SP2 with all known patches
If you open one of the maintenance forms for backing up or restoring a
database, the form isn’t wide enough to display the browse button for
selecting the file to backup into or restore from. I c
On 4 Dec 2006 at 11:50, Patrick Headley wrote:
> If you open one of the maintenance forms for backing up or restoring a
> database, the form isn't wide enough to display the browse button for
> selecting the file to backup into or restore from. I checked this on
I've encountered that tooyou
PGAdmin III v1.6.1 binary install
Windows XP SP2 with all known patches
If you open one of the maintenance forms for backing up or restoring a
database, the form isn't wide enough to display the browse button for
selecting the file to backup into or restore from. I checked this on v1.4.2
and i
A.j. Langereis wrote:
To whom it may concern,
My pgAdmin crashed when I tried to vacuum the "template0" database. It
is of course not needed to vacuum this database, but I clicked on it by
accident. When I tried it again, this time on purpose, it happened again.
This is caused by launching
To whom it may concern,
My pgAdmin crashed when I tried to vacuum the "template0" database. It is
of course not needed to vacuum this database, but I clicked on it by accident.
When I tried it again, this time on purpose, it happened again.
The PostgreSQL database that is used is v8.0.4, t
Cook, Tom wrote:
Platform information:
- MS Windows 2000
- English (US)
- Binary distribution
- Version 1.2.1
Tip of the Day claims that "The meaning of Life, the Universe and Everything is 42."
This is of course incorrect; in fact, "The answer to the question
Platform information:
- MS Windows 2000
- English (US)
- Binary distribution
- Version 1.2.1
Tip of the Day claims that "The meaning of Life, the Universe and Everything is
42." This is of course incorrect; in fact, "The answer to the question of
Life, the Univer
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Howard Cole
> Sent: 09 June 2005 08:40
> To: pgadmin-support@postgresql.org
> Subject: [pgadmin-support] Bug in pgadmin dump
>
> Hi,
>
> there is a problem with the
Hi,
there is a problem with the backup utility when creating a plain backup
- when you select data-only and select the disable triggers option, the
triggers are not disabled. (i.e. it does not add "--disable-triggers" or
"-X" to the command line.
Version: 1.2.1
OS Win XP SP2
Distribution: Po
Marcel Gsteiger wrote:
Hi all,
I just wanted to report a small bug in PGAdmin III, probably regarding quoting.
In a PostgreSQL 8.0 database for a school, I have a table named "class" in a
schema named exnr. When I do the following:
right-click / properties on the table named &qu
Hi all,
I just wanted to report a small bug in PGAdmin III, probably regarding quoting.
In a PostgreSQL 8.0 database for a school, I have a table named "class" in a
schema named exnr. When I do the following:
right-click / properties on the table named "class", then "
I cannot create a foreign key that has three primary
keys. The okay button in pgadmin III remains shaded on
the third column.
__
Do you Yahoo!?
Meet the all-new My Yahoo! - Try it today!
http://my.yahoo.com
---(end o
] Bug in
PGAdmin III 1.2.0 Beta
Hi, I
don’t known if that`s a bug:
when i
create a new table, and i include a varchar o char field, i obtain this error
: "Error: syntax error at or near "(" at character
xxx"
the bug
is in the specif
Title: Mensaje
Hi, I don’t known if
that`s a bug:
when i create a new table,
and i include a varchar o char field, i obtain this error : "Error: syntax
error at or near "(" at character xxx"
the bug is in the
specification of sql query, varchar, char datatypes are quoted
[EMAIL PROTECTED] wrote:
Server = PostgreSQL v7.4.2 on SuSE Linux 9.1
PgAdminIII v1.1.0 Devel(Apr 14 2004) on Windows 2000-sp4
Using the ddl created by the create table & index UI wizards I then
post that ddl into the query window and hit explain. I receive and
error message that some syntax is i
Title: Explain Bug in PgAdmin III Query window
Server = PostgreSQL v7.4.2 on SuSE Linux 9.1
PgAdminIII v1.1.0 Devel(Apr 14 2004) on Windows 2000-sp4
Using the ddl created by the create table & index UI wizards I then post that ddl into the query window and hit explain. I receive and e
Michalis Kabrianis wrote:
Hi
I think I found a bug regarding privileges in pgadmin III
To replicate:
create a user in postgres named "arwdxt" (not all letters needed of
course :)
Create another user named temp_user
as user "arwdxt" create a table test_table
REVOKE all ON test_table FROM temp_user
Hi
I think I found a bug regarding privileges in pgadmin III
To replicate:
create a user in postgres named "arwdxt" (not all letters needed of
course :)
Create another user named temp_user
as user "arwdxt" create a table test_table
REVOKE all ON test_table FROM temp_user
GRANT SELECT ON test_table
Alexandr S wrote:
Hi
There is bug in Pgadmin 1.0.1 . When problems starts, Pgadmin
suddenly shut down every time I try to insert my samples ( 6 samples
are attached to this letter) . This is true only for databases in KOI8
encoding (for database in unicode encoding all this problems absent
Hi
There is bug in Pgadmin 1.0.1 . When problems starts, Pgadmin suddenly
shut down every time I try to insert my samples ( 6 samples are attached
to this letter) . This is true only for databases in KOI8 encoding (for
database in unicode encoding all this problems absent, all works
right
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Sent: 18 November 2003
08:12To: [EMAIL PROTECTED]Subject: Re:
[pgadmin-support] bug in pgadmin III
Hi, I originally meant that the password inputbox shows the password
like "mypassword" an
[EMAIL PROTECTED]
An: "Christopher Kings-Lynne" <[EMAIL PROTECTED]>
Kopie: "Andreas Pflug" <[EMAIL PROTECTED]>, "Michiel Lange" <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
Thema: Re: [pgadmin-support] bug in pgadmin III
&
> -Original Message-
> From: Christopher Kings-Lynne [mailto:[EMAIL PROTECTED]
> Sent: 18 November 2003 01:19
> To: Dave Page
> Cc: Andreas Pflug; Michiel Lange; [EMAIL PROTECTED]
> Subject: Re: [pgadmin-support] bug in pgadmin III
>
>
> >>If you kno
If you know how to encrypt the password, we certainly could
supply the option to enter it that way...
It's just an md5 hash prefixed with 'md5' isn't it?
???
Don't you just go ALTER USER blah ENCRYPTED PASSWORD 'asdf';
And postgres itself will encrypt it for you.
Your SQL view should show wh
> -Original Message-
> From: Andreas Pflug [mailto:[EMAIL PROTECTED]
> Sent: 17 November 2003 17:19
> To: Dave Page
> Cc: Michiel Lange; [pgADMIN]
> Subject: Re: [pgadmin-support] bug in pgadmin III
>
> IMHO this isn't worth the effort. We have SSL
Dave Page wrote:
Saves sending it in plaintext over the wire, or displaying it on screen
anywhere.
IMHO this isn't worth the effort. We have SSL connections to secure wire
tapping. This is necessary for securing session logon anyway.
Regards,
Andreas
---(end of bro
> -Original Message-
> From: Andreas Pflug [mailto:[EMAIL PROTECTED]
> Sent: 17 November 2003 16:45
> To: Michiel Lange; [pgADMIN]
> Subject: Re: [pgadmin-support] bug in pgadmin III
>
> Michiel Lange wrote:
>
> >Well... I thought PgAdmin sends SQL c
Michiel Lange wrote:
Well... I thought PgAdmin sends SQL commands to the database, right?
As you can see on each property dialog's SQL page.
So, if you do
CREATE USER WITH ENCRYPTED PASSWD ''?
ENCRYPTED PASSWORD is for dump/restore purposes (i.e. if you don't know
the plain text password)
> -Original Message-
> From: Andreas Pflug [mailto:[EMAIL PROTECTED]
> Sent: 17 November 2003 16:23
> To: Dave Page
> Cc: Michiel Lange; [EMAIL PROTECTED]
> Subject: Re: [pgadmin-support] bug in pgadmin III
>
> Ok, so we require pgAdmin3 users to calculate the
Dave Page wrote:
Wouldn't it be better to use
CREATE ENCRYPTED passwd instead? Me thinks that's a better solution
anyway!
If you know how to encrypt the password, we certainly could
supply the option to enter it that way...
It's just an md5 hash prefixed with 'md5' isn't it?
> -Original Message-
> From: Andreas Pflug [mailto:[EMAIL PROTECTED]
> Sent: 17 November 2003 16:07
> To: Michiel Lange
> Cc: [EMAIL PROTECTED]
> Subject: Re: [pgadmin-support] bug in pgadmin III
>
> Michiel Lange wrote:
>
> >Wouldn't it be be
Michiel Lange wrote:
Wouldn't it be better to use
CREATE ENCRYPTED passwd instead? Me thinks that's a better solution
anyway!
If you know how to encrypt the password, we certainly could supply the
option to enter it that way...
Regards,
Andreas
---(end of broadcast)
bject:Re: [pgadmin-support] bug in pgadmin III
Hi Tom,
[EMAIL PROTECTED] wrote:
>
> - in Create Usergroup : the property-page contains fields like
> *Username *and *User-ID* but should contain *Groupname *and *Group-ID*
This is a typo, fixed in cvs now.
> - in Create User :
Hi Tom,
[EMAIL PROTECTED] wrote:
- in Create Usergroup : the property-page contains fields like
*Username *and *User-ID* but should contain *Groupname *and *Group-ID*
This is a typo, fixed in cvs now.
- in Create User : the property-page contains a password-field which
shows passwords in plain
Hi,
I found several bug's (perhaps easy to solve) in pgAdmin III 1.1.0 devel.
- in Create Usergroup : the property-page contains fields like Username and User-ID but should contain Groupname and Group-ID
- in Create User : the property-page contains a password-field which shows passwords in plai
Godshall Michael wrote:
Ok,
In pgadminII I could choose to output the results directly to a text
file without having them first displayed on the screen. That is what
I was really trying to do(I normally don't try to read the 5000
characters in the pgadmin window).
Is their a way to do this i
Godshall Michael wrote:
I use linux at home and would test it there if I can get pgadminIII
installed on it. Last time I tried it failed because I did not have
ssl and crypto so.4 libraries. My Redhat 8.0 box has versions so.2.
Maybe I downloaded the wrong version of pgadminIII.
Adam,
can'
Title: RE: [pgadmin-support] Bug in pgadmin III displaying/exporting data from query window(tr uncating)
Ok,
In pgadminII I could choose to output the results directly to a text file without having them first displayed on the screen. That is what I was really trying to do(I normally don&#
Godshall Michael wrote:
Hi,
I am running version 1.0.0, Win2k, english version, and postgresql
7.3.4 under cygwin.
In the File->Options->Query->max. characters per column I have changed
the default to 5000 characters. When I run a query in a pgadminIII
the columns that I have defined as t
Hi,
I am running version
1.0.0, Win2k, english version, and postgresql 7.3.4 under cygwin.
In the
File->Options->Query->max. characters per column I have changed the
default to 5000 characters. When I run a query in a pgadminIII the columns
that I have defined as text stop displaying
Thanks
for the bug report. This is now fixed in the CVS code.
Regards, Dave.
-Original Message-From: Leandro M.
Araujo [mailto:[EMAIL PROTECTED]] Sent: 06 February 2002
11:35To: [EMAIL PROTECTED]:
[pgadmin-support] Bug in PgAdmin
Helo.
I find an bug in the
Helo.
I find an bug in the Upgrade Wizard
I am from Brazil, and work with PgAdmin to
administrate my databases.
When i click in Upgrade Wizard to Update my system
the aplication conect in the server to request the information of version. The
list form show me 3 itens. But a click in Pre
80 matches
Mail list logo
