[pgadmin-support] Error Message

2003-07-15 Thread Germano Rizzo
-- System Information --

Platform:   Windows 2000
Version:5.0
Build:  2195 Service Pack 3

-- Application Information --

Name:   pgAdmin II
Version:1.5.60
Descripton: 

Name:   pgSchema
Version:1.5.60
Descripton: PostgreSQL Schema Objects v1.5.60

-- Database Information --

Version:0.0.0
Descripton: 

-- Driver Information --

Name:   
Version:0.0.0
Descripton: 

-- Error Information --

Description:'Visible' property can't be set on this control
Number: 387
Routine:pgAdmin II:basMisc.BuildPluginsMenu



Insert your comment:


---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
  subscribe-nomail command to [EMAIL PROTECTED] so that your
  message can get through to the mailing list cleanly


[pgadmin-support] Error Message

2003-07-15 Thread Yassin Idris



 
-- System Information --Platform: Windows 2000Version: 
5.0Build: 2195 Service Pack 3-- Application Information 
--Name: pgAdmin IIVersion: 1.5.60Descripton: Name: 
pgSchemaVersion: 1.5.60Descripton: PostgreSQL Schema Objects 
v1.5.60-- Database Information --Version: 7.2.3Descripton: 
PostgreSQL 7.2.3 on i686-pc-linux-gnu, compiled by GCC 2.96-- Driver 
Information --Name: PostgreSQLVersion: 7.3.100Descripton: 
PostgreSQL 7.2.3 on i686-pc-linux-gnu, compiled by GCC 2.96-- Error 
Information --Description: Type mismatchNumber: 13Routine: 
pgAdmin 
II:frmMain.mnuPluginsPlg_ClickI 
following the instruction and installed the migration plugins.  But when 
ever I attempt to use the "DB migration wizard", I encounter the above 
error.  I am not able to proceed.  
 
How can I overcome this problem?  What is 
missing?  Any help is highly appreciated.
 
 
Yassin Idris


Re: [pgadmin-support] Error Message

2003-07-15 Thread Dave Page
Title: Message



 

  
  -Original Message-From: Yassin Idris 
  [mailto:[EMAIL PROTECTED] Sent: 14 July 2003 
  23:23To: [EMAIL PROTECTED]Cc: 
  [EMAIL PROTECTED]Subject: [pgadmin-support] Error 
  Message
  Description: Type 
  mismatchNumber: 13Routine: pgAdmin 
  II:frmMain.mnuPluginsPlg_ClickI 
  following the instruction and installed the migration plugins.  But when 
  ever I attempt to use the "DB migration wizard", I encounter the above 
  error.  I am not able to proceed.  
   
  How can I overcome this problem?  What is 
  missing?  Any help is highly appreciated.
   
It sounds 
like you have the wrong version of the plugin for your version of pgAdmin. 
Please make sure you downloaded the correct version.
 
Regards, 
Dave.


Re: [pgadmin-support] Error Message

2003-07-15 Thread Dave Page


> -Original Message-
> From: Germano Rizzo [mailto:[EMAIL PROTECTED] 
> Sent: 14 July 2003 18:20
> To: [EMAIL PROTECTED]
> Subject: [pgadmin-support] Error Message
> 
> 
> Description:  'Visible' property can't be set on this control
> Number:   387
> Routine:  pgAdmin II:basMisc.BuildPluginsMenu
> 
> 

Hi, can you please recreate this error with logging set to Full Debug
(under Tools -> Options), and send the resulting logfile?

Thanks, Dave.

---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings


[pgadmin-support] pgadmin III connection dialogue: cannot change options

2003-07-15 Thread Troels Arvin
Hello,

>From latest CVScheckout:

When trying to connect to a server (the "connect to server" dialogue),
it seems that the connection options (like user name) cannot be changed.
Current work-around: Remove the connection and create a new one with
other parameters.

-- 
Greetings from Troels Arvin, Copenhagen, Denmark

---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]


Re: [pgadmin-support] pgadmin III connection dialogue: cannot change options

2003-07-15 Thread Dave Page


> -Original Message-
> From: Troels Arvin [mailto:[EMAIL PROTECTED] 
> Sent: 15 July 2003 12:01
> To: [EMAIL PROTECTED]
> Subject: [pgadmin-support] pgadmin III connection dialogue: 
> cannot change options
> 
> 
> Hello,
> 
> >From latest CVS  checkout:
> 
> When trying to connect to a server (the "connect to server" 
> dialogue), it seems that the connection options (like user 
> name) cannot be changed. Current work-around: Remove the 
> connection and create a new one with other parameters.

That's by design (and has always been that way).

Regards, Dave.

---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings


Re: [pgadmin-support] pgadmin III connection dialogue: cannot change

2003-07-15 Thread Andreas Pflug
Troels Arvin wrote:

Hello,

From latest CVS	checkout:
When trying to connect to a server (the "connect to server" dialogue),
it seems that the connection options (like user name) cannot be changed.
That' right, but why change parameters? Do you do that regularly? If you 
need more than one user, why not creating more connections.

Regards,
Andreas
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
 subscribe-nomail command to [EMAIL PROTECTED] so that your
 message can get through to the mailing list cleanly


Re: [pgadmin-support] pgadmin III connection dialogue: cannot

2003-07-15 Thread Troels Arvin
Hello,

On Tue, 2003-07-15 at 13:12, Andreas Pflug wrote:
> >When trying to connect to a server (the "connect to server" dialogue),
> >it seems that the connection options (like user name) cannot be changed.
> >
> That' right, but why change parameters? Do you do that regularly? If you 
> need more than one user, why not creating more connections.

You may have a point. But maybe the dialogue could be changed, then? - In a way where 
the fields don't look like they are editable (but still cut-and-past'able, if 
possible)?

-- 
Greetings from Troels Arvin, Copenhagen, Denmark

---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster


[pgadmin-support] pgAdmin3: adding comments to existing tables

2003-07-15 Thread Terence Kearns
because the interface attempts to "re-submit all" of the properties of 
the existing table for alteration, if you want to change any one 
property of a table, you need to re-apply all properties. This has the 
undesired side-effect of failing *any* modification to a table if any of 
the other *existing* properties fail to qualify for re-applying through 
ALTERing.

For instance, I have a table containing a column with a default value.

When I try to use pgAdmin3 to add(modify) a(the) comment to that table, 
the operation fails with the message.

ERROR: Adding columns with defaults is not implementd...

This is silly bacause my intent was not to add a column. I think this 
may be a user-interface design limitation.

--
Terence Kearns ~ ph: +61 2 6201 5516
IT Database/Applications Developer
Enterprise Information Systems
Client Services Division
University of Canberra
www.canberra.edu.au
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster