[pgadmin-support] Error Message

2003-07-12 Thread Swapnil 



 -- 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: 
0.0.0Descripton: -- Driver Information --Name: Version: 
0.0.0Descripton: -- Error Information --Description: Could 
not connect to the serverBCould not connect to remote socket.Number: 
-2147467259Routine: pgAdmin 
II:frmConnect.cmdConnect_ClickInsert 
your comment:

Re: [ADMIN] [pgadmin-support] Overloading functions that are used by operators.

2003-07-12 Thread Tom Lane 
"Dave Page" <[EMAIL PROTECTED]> writes:
> Well I always thought you could overload functions in this way, however
> with your example below, although it creates it OK, PostgreSQL (not
> pgAdmin) gives the error 'ERROR: There is more than one function named
> textcat'.

I see no such error here ...

regression=# create function pg_catalog.textcat(varchar,text)
regression-# returns text as 'textcat' language 'internal';
CREATE FUNCTION


regards, tom lane

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

[pgadmin-support] Error Message

2003-07-12 Thread 김경수 



 -- System Information --Platform: Windows 
2000Version: 5.0Build: 2195 Service Pack 4-- Application 
Information --Name: pgAdmin IIVersion: 1.5.60Descripton: 
Name: pgSchemaVersion: 1.5.60Descripton: PostgreSQL Schema 
Objects v1.5.60-- Database Information --Version: 
7.3.2Descripton: PostgreSQL 7.3.2 on i686-pc-linux-gnu, compiled by GCC 
2.96-- Driver Information --Name: PostgreSQLVersion: 
7.3.100Descripton: PostgreSQL 7.3.2 on i686-pc-linux-gnu, compiled by GCC 
2.96-- Error Information --Description: ERROR:  must be 
called under standalone postgres with -O -P optionsNumber: 
-2147467259Routine: pgAdmin 
II:basActions.ReindexInsert 
your comment:

[pgadmin-support] Error Message

2003-07-12 Thread Marcos Tadeu P Vargens 
-- 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:7.2.1
Descripton: PostgreSQL 7.2.1 on i686-pc-linux-gnu, compiled by GCC 2.95.4

-- Driver Information --

Name:   PostgreSQL
Version:7.3.100
Descripton: PostgreSQL 7.2.1 on i686-pc-linux-gnu, compiled by GCC 2.95.4

-- Error Information --

Description:Control array element '1' doesn't exist
Number: 340
Routine:pgAdmin II:frmSQLOutput.cmdDelete_Click



Insert your comment:



---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

[pgadmin-support] Error Message

2003-07-12 Thread narkeassocia 



 
-- 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.3.3Descripton: 
PostgreSQL 7.3.3 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2 20020903 
(Red Hat Linux 8.0 3.2-7)-- Driver Information --Name: 
PostgreSQLVersion: 7.3.100Descripton: PostgreSQL 7.3.3 on 
i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2 20020903 (Red Hat Linux 8.0 
3.2-7)-- Error Information --Description: ERROR:  parser: 
parse error at or near "(" at character 47Number: -2147467259Routine: 
pgAdmin 
II:frmTable.cmdOK_ClickInsert 
your comment: When I tried to import a column for an existing table into a new 
table
using "Import" buttom on  "Column" page of "Create Table" dialog 
box.
 
Ajay Narke 
BEGIN:VCARD
VERSION:2.1
N:Narke;Ajay;J;Mr
FN:Ajay J Narke
NICKNAME:Ajay
ORG:Narke Associates
TITLE:Proprietor
TEL;WORK;VOICE:+91-231-2621701
TEL;HOME;VOICE:+91-231-2626126
TEL;CELL;VOICE:+91-94224-13843
ADR;WORK;ENCODING=QUOTED-PRINTABLE:;;F-2, G.N.Chambers=0D=0AKolekar Tockty=0D=0AB Ward, Mangalwar Peth;Kolhapur=
;Maharashtra;416012;India/Asia
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:F-2, G.N.Chambers=0D=0AKolekar Tockty=0D=0AB Ward, Mangalwar Peth=0D=0AKolha=
pur, Maharashtra 416012=0D=0AIndia/Asia
ADR;HOME;ENCODING=QUOTED-PRINTABLE:;;F-6, G.N.Chambers=0D=0AKolekar Tockty=0D=0AB Ward, Mangalwar Peth;Kolhapur=
;Maharashtra;416012;India/Asia
LABEL;HOME;ENCODING=QUOTED-PRINTABLE:F-6, G.N.Chambers=0D=0AKolekar Tockty=0D=0AB Ward, Mangalwar Peth=0D=0AKolha=
pur, Maharashtra 416012=0D=0AIndia/Asia
X-WAB-GENDER:2
URL;WORK:http://www.narkeassociates.com
EMAIL;PREF;INTERNET:[EMAIL PROTECTED]
REV:20030711T09Z
END:VCARD

---(end of broadcast)---
TIP 6: Have you searched our list archives?

   http://archives.postgresql.org

Re: [pgadmin-support] Error Message

2003-07-12 Thread Dave Page 
It's rumoured that ±è°æ¼ö once said:>
> Description: ERROR:  must be called under standalone postgres with -O
> -P options
 Number: -2147467259
> Routine: pgAdmin II:basActions.Reindex

Hi,

What table were you trying to reindex when this error occured?

Regards, Dave



---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
  joining column's datatypes do not match

Re: [pgadmin-support] Error Message

2003-07-12 Thread Dave Page 
It's rumoured that Marcos Tadeu P Vargens once said:
>
> Description:  Control array element '1' doesn't exist
> Number:   340
> Routine:  pgAdmin II:frmSQLOutput.cmdDelete_Click

Hi,

Can you recreate this error with logging set to Full Debug and send the
resulting logfile please?
Regards, Dave



---(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] pgadminIII bug

2003-07-12 Thread Dave Page 


> -Original Message-
> From: George T. Gibson [mailto:[EMAIL PROTECTED] 
> Sent: 10 July 2003 20:33
> To: [EMAIL PROTECTED]
> Subject: [pgadmin-support] pgadminIII bug
> 
> 
> When trying to alter a sequence value, the below SQL is issued...
> 
> SELECT setval(public.part_part_id_key, 3479);
> 
> Then I get...
> 
> ERROR:  Relation "public" does not exist

Thanks George,  fixed in CVS.

Regards, Dave.

---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
  joining column's datatypes do not match

Re: [pgadmin-support] Error Message

2003-07-12 Thread Dave Page 
Title: Message



 

  
  -Original Message-From: 
  [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
  Sent: 11 July 2003 10:11To: 
  [EMAIL PROTECTED]Subject: [pgadmin-support] Error 
  Message
  -- Error Information 
  --Description: ERROR:  parser: parse error at or near "(" at 
  character 47Number: -2147467259Routine: pgAdmin 
  II:frmTable.cmdOK_ClickInsert 
  your comment: When I tried to import a column for an existing table into a new 
  table
  using "Import" buttom on  "Column" page of "Create Table" 
  dialog box.
   
   
Hi,
 
I cannot reproduce this - can you do so with debugging 
set to Full Debug (under Tools -> Options) and email the resulting 
logfile please?
 
Thanks, Dave.

[pgadmin-support] BUG: pgAdmin III - Vacuuming executes incorrect statement

2003-07-12 Thread Matej Rizman 
Version: pgAdmin III, version 0.8.0 Devel (Jul 10 2003).

Steps to reproduce error:
1) connect to database
2) select arbitrary table
3) Tools->Reorganize
4) Select Vacuum (or Analyze, this causes similar error) in dialog box
5) Press Ok.

pgAdmin III executes the following statement to PostgreSQL:
VACUUM VERBOSE ANALYZE Table public.table_name


The correct statement would omit word "Table" and it would be:
VACUUM VERBOSE ANALYZE public.table_name

pgAdmin III also does not inform user about error that occured during VACUUM. 

Regards, 
Matej Rizman








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

Re: [pgadmin-support] BUG: pgAdmin III - Vacuuming executes incorrect statement

2003-07-12 Thread Dave Page 


> -Original Message-
> From: Matej Rizman [mailto:[EMAIL PROTECTED] 
> Sent: 12 July 2003 21:09
> To: [EMAIL PROTECTED]
> Subject: [pgadmin-support] BUG: pgAdmin III - Vacuuming 
> executes incorrect statement
> 
> 
> Version: pgAdmin III, version 0.8.0 Devel (Jul 10 2003).
> 
> Steps to reproduce error:
> 1) connect to database
> 2) select arbitrary table
> 3) Tools->Reorganize
> 4) Select Vacuum (or Analyze, this causes similar error) in dialog box
> 5) Press Ok.
> 
> pgAdmin III executes the following statement to PostgreSQL: 
> VACUUM VERBOSE ANALYZE Table public.table_name

Thanks, fixed in CVS.

Regards, Dave.

---(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] Migration Wizard - Access 97 Autonumber

2003-07-12 Thread D Tim Cummings 
I am trying to migrate an Access 97 database to PostgreSQL 7.3 using 
pgAdmin 1.4.12 and the Migration Wizard 1.4.12.  I want to keep using 
the Access 97 front end connected to the PostgreSQL backend.

The default type mapping didn't work for me but I discovered that 
mapping
  Boolean -> int2 (instead of bool) and
  Currency -> float8 (instead of money)
meant I needed no changes to my Access97 front end.

The problem I had was the Autonumber mapping.  By default Autonumber 
maps to int8 which causes Access 97 to think all records in the linked 
table are deleted.  If the PostgreSQL data type is changed to int4, 
Access97 works fine.

I noticed in the mailing list archives on 05 Dec 2002, a subscriber 
mentioned that he needed int8 for autonumber fields to migrate for his 
version of Access, which I can only assume is later than Access 97.  
Dave Page replied that he had now changed it from int4.  It would be 
handy if this feature was selectable like the other type maps, so that 
neither myself, nor the original subscriber are placed in the position 
of having to drop the migrated table just to fix the data type of the 
Autonumber field.

Otherwise this is a great program that has already saved me many hours 
of work.

Tim Cummings

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