Thread: Problems using PGAdmin III

Problems using PGAdmin III

From
Együd Csaba
Date:
Dear Jean-Michel,
I'm succeeded to subscribe this list. Thank you.

> You can register the support mailing list from:
> http://www.pgadmin.org/pgadmin3/support.php#support_list
Done.

> The euro display problem is an encoding problem. The euro sign is not part
of
> an ASCII database. Whenever you would like Euro support, choose:
>
> Database->Create Database and select dropdown menu:
> Latin9 (Iso-8859-15) or Unicode encoding.
To tell the truth it wasn't what I wnated. Actually I can insert the euro
sign via ODBC using pure SQL_ASCII encoding. PGAdmin can display the euro
sign. The only problem is that it can't display which was inserted with it.
I can't use unicode encoding, because the client machines are win9x which
does not support unicode (as far as I know). It's not a crucial problem, but
it's an inconvenience.

> Give us more details about the function problem and we will make our best
to
> help you. Let's continue on pgAdmin3 mailing list... What version of
pgAdmin3
> are you using (answer us on pgAdmin3 mailing list)?
I've downloaded the latest development version (1.1.0) and the phenomenon is
the same. If it is necessary I will quote the whole source of one of my
"missing" functions. Actually there are several functions which are hidden
from pgadmin. There is no special reason (syntax error, missing quote - it
is a running system and these are frequently used functions) to hide the
function body so I have no idea.
The content of the previev pane in case of one of the false functions:
**********************************************************************
-- Function: public.close_back_invoice(int4, int4, int4)

-- DROP FUNCTION public.close_back_invoice(int4, int4, int4);

CREATE OR REPLACE FUNCTION public.close_back_invoice(int4, int4, int4) RETURNS bool AS
'' LANGUAGE 'plpgsql' VOLATILE;
**********************************************************************

The real content is in the attached file (func.dump).

Thank you in advance for your help.

Best Regards,

-- Csaba

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.530 / Virus Database: 325 - Release Date: 2003. 10. 22.



Re: Problems using PGAdmin III

From
Andreas Pflug
Date:
Együd Csaba wrote:

>Dear Jean-Michel,
>I'm succeeded to subscribe this list. Thank you.
>
>  
>
>>You can register the support mailing list from:
>>http://www.pgadmin.org/pgadmin3/support.php#support_list
>>    
>>
>Done.
>
>  
>
>>The euro display problem is an encoding problem. The euro sign is not part
>>    
>>
>of
>  
>
>>an ASCII database. Whenever you would like Euro support, choose:
>>
>>Database->Create Database and select dropdown menu:
>>Latin9 (Iso-8859-15) or Unicode encoding.
>>    
>>
>To tell the truth it wasn't what I wnated. Actually I can insert the euro
>sign via ODBC using pure SQL_ASCII encoding. PGAdmin can display the euro
>sign. The only problem is that it can't display which was inserted with it.
>I can't use unicode encoding, because the client machines are win9x which
>does not support unicode (as far as I know). It's not a crucial problem, but
>it's an inconvenience.
>  
>
You *can* use unicode, if you set the client encoding to a codeset your 
machine supports (might be Latin9). SQL_ASCII looks convenient, but when 
it comes to multilanguage it's a real pain, so it's better to designate 
what the data really is.

Regards,
Andreas




Re: Problems using PGAdmin III

From
Együd Csaba
Date:
Hi Andreas,
thank you, I'll make a try. It should eliminate the euro problem as well.

-- Csaba

> -----Original Message-----
> From: pgadmin-support-owner@postgresql.org
> [mailto:pgadmin-support-owner@postgresql.org]On Behalf Of
> Andreas Pflug
> Sent: Sunday, October 26, 2003 7:21 PM
> To: csegyud@vnet.hu
> Cc: Pgadmin-Support (E-mail)
> Subject: Re: [pgadmin-support] Problems using PGAdmin III
>
>
> Együd Csaba wrote:
>
> >Dear Jean-Michel,
> >I'm succeeded to subscribe this list. Thank you.
> >
> >
> >
> >>You can register the support mailing list from:
> >>http://www.pgadmin.org/pgadmin3/support.php#support_list
> >>
> >>
> >Done.
> >
> >
> >
> >>The euro display problem is an encoding problem. The euro
> sign is not part
> >>
> >>
> >of
> >
> >
> >>an ASCII database. Whenever you would like Euro support, choose:
> >>
> >>Database->Create Database and select dropdown menu:
> >>Latin9 (Iso-8859-15) or Unicode encoding.
> >>
> >>
> >To tell the truth it wasn't what I wnated. Actually I can
> insert the euro
> >sign via ODBC using pure SQL_ASCII encoding. PGAdmin can
> display the euro
> >sign. The only problem is that it can't display which was
> inserted with it.
> >I can't use unicode encoding, because the client machines
> are win9x which
> >does not support unicode (as far as I know). It's not a
> crucial problem, but
> >it's an inconvenience.
> >
> >
> You *can* use unicode, if you set the client encoding to a
> codeset your
> machine supports (might be Latin9). SQL_ASCII looks
> convenient, but when
> it comes to multilanguage it's a real pain, so it's better to
> designate
> what the data really is.
>
> Regards,
> Andreas
>
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
>                http://archives.postgresql.org
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.530 / Virus Database: 325 - Release Date: 2003. 10. 22.
>

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.530 / Virus Database: 325 - Release Date: 2003. 10. 22.