Skip site navigation (1) Skip section navigation (2)

Re: idea for reading encodign format

From: frank_lupo <frank_lupo(at)email(dot)it>
To: dpage <dpage(at)vale-housing(dot)co(dot)uk>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: idea for reading encodign format
Date: 2002-09-10 15:33:40
Message-ID: H28B84$227DB3BE406A7B2E3B273C7690C2E8B8@email.it (view raw or flat)
Thread:
Lists: pgadmin-hackers
I using  PostgreSQL 7.2
template1=# select version();
                          version
------------------------------------------------------------
 PostgreSQL 7.2 on i686-pc-cygwin, compiled by GCC 2.95.3-5
(1 row)

I tried on 2  systems:

template1=# select  versin();
                            version
--------------------------------------------------------------
 PostgreSQL  7.3b1 on i686-pc-cygwin, compiled by GCC 2.95.3-5
(1 row)

template1=# select  pg_encoding_to_char(0)
template1-# union select  pg_encoding_to_char(1)
template1-# union select  pg_encoding_to_char(2)
template1-# union select  pg_encoding_to_char(3)
template1-# union select  pg_encoding_to_char(4)
template1-# union select  pg_encoding_to_char(5)
template1-# union select  pg_encoding_to_char(6)
template1-# union select  pg_encoding_to_char(7)
template1-# union select  pg_encoding_to
 _char(8)
0D
template1-# union select  pg_encoding_to_char(9)
template1-# union select  pg_encoding_to_char(10)
template1-# union select  pg_encoding_to_char(11)
template1-# union select  pg_encoding_to_char(12)
template1-# union select  pg_encoding_to_char(13)
template1-# union select  pg_encoding_to_char(14)
template1-# union select  pg_encoding_to_char(15)
template1-# union select  pg_encoding_to_char(16)
template1-# union select  pg_encoding_to_char(17)
template1-# union select  pg_encoding_to_char(18)
template1-# union select  pg_encoding_to_char(19)
template1-# union select  pg_encoding_to_char(20)
template1-# union select  pg_encoding_to_char(21);
 pg_encoding_to_char
---------------------
 EUC_CN
 EUC_JP
 EUC_KR
 EUC_TW
 JOHAB
 KOI8
 LATIN1
 LATIN10
 LATIN2
 LATIN3
 LATIN4
 LATIN5
 LATIN6
 LATIN7
 LATIN8
 LATIN9
 MULE_INTER
 NAL
=0
A
 SQL_ASCII
 TCVN
 UNICODE
 WIN1256
 WIN874
(22  rows)

and

template1=>  select  version();
                               version
-------------------------------------------------------------------
 PostgreSQL  7.2 on i686-pc-linux-gnu, compiled by GCC egcs-2.91.66
(1  row)

template1=>  select pg_encoding_to_char(0)
template1-> union select  pg_encoding_to_char(1)
template1-> union select  pg_encoding_to_char(2)
template1-> union select  pg_encoding_to_char(3)
template1-> union select  pg_encoding_to_char(4)
template1-> union select  pg_encoding_to_char(5)
template1-> union select  pg_encoding_to_char(6)
template1-> union select  pg_encoding_to_char(7)
template1-> union select  pg_encoding_to_char(8)
template1-> union select  pg_encoding_to_char(9)
template1-> union select  pg_encoding_to_char(10)
template1-> union select  pg_encoding_to_char
 (11)
0
Atemplate1-> union select  pg_encoding_to_char(12)
template1-> union select  pg_encoding_to_char(13)
template1-> union select  pg_encoding_to_char(14)
template1-> union select  pg_encoding_to_char(15)
template1-> union select  pg_encoding_to_char(16)
template1-> union select  pg_encoding_to_char(17)
template1-> union select  pg_encoding_to_char(18)
template1-> union select  pg_encoding_to_char(19)
template1-> union select  pg_encoding_to_char(20)
template1-> union select  pg_encoding_to_char(21);
 pg_encoding_to_char
---------------------
 SQL_ASCII
(1  row)

The 7.2 system was  compiled without multibyte support. In 7.3, multibyte is always on. I guess  it probably doesn't matter much as it's obviously giving only useful encodings,  the problem is this (on the 7.2 system):

template1=>  select  pg_encoding_to_char(45);
 pg_encoding_to_char
---------------------
 SQL_ASCII
 
(1  r
o
w)

template1=>  select  pg_encoding_to_char(450);
 pg_encoding_to_char
---------------------
 SQL_ASCII
(1  row)

How would the loop  know when to give up and exit?

Regards,  Dave.
  
  -----Original Message-----
From: frank_lupo    [mailto:frank_lupo(at)email(dot)it] 
Sent: 10 September 2002    14:45
To: Dave Page
Cc: pgadmin-hackers
Subject:    RE: [pgadmin-hackers] idea for reading encodign format


  
  
I replace this code in frmdatabase pgadmin2. I don't have this problem.  
  
What is your result if you execute this selection ?
  
select pg_encoding_to_char(0) 
  
union select pg_encoding_to_char(1)
  
union select    pg_encoding_to_char(2)
  
union select    pg_encoding_to_char(3)
  
union select    pg_encoding_to_char(4)
  
union select    pg_encoding_to_char(5)
  
union select    pg
 _encodin
g
_to_char(6)
  
union select    pg_encoding_to_char(7)
  
union select    pg_encoding_to_char(8)
  
union select    pg_encoding_to_char(9)
  
union select    pg_encoding_to_char(10)
  
union select    pg_encoding_to_char(11)
  
union select    pg_encoding_to_char(12)
  
union select    pg_encoding_to_char(13)
  
union select    pg_encoding_to_char(14)
  
union select    pg_encoding_to_char(15)
  
union select    pg_encod! ing_to_ch a r(16)
  
union select    pg_encoding_to_char(17)
  
union select    pg_encoding_to_char(18)
  
union select    pg_encoding_to_char(19)
  
union select    pg_encoding_to_char(20)
  
union select pg_encoding_to_char(21)
  
My result is :
  
 pg_encoding_to_char
---------------------
 ALT
 EUC_CN
 EUC_JP
 EUC_KR
 EUC_TW
 ISO_8859_5
 ISO_8859_6 0D
 KO
I
8
 LATIN1
 LATIN10
 LATIN2
 LATIN3
 LATIN4
 LATIN5
 LATIN6
 LATIN7
 LATIN8
 LATIN9
 MULE_INTERNAL
&!    nbsp;SQL_ A SCII
 UNICODE
 WIN
(22 rows)
  
The order is not by number encoding.
  

       
Hi  Frank,
    
    
Hmm, that doesn't seem to work here. For any random integervalue of X       that I try in select pg_encoding_to_char(X), I get SQL_ASCII as the       result.
    
    
This       is a problem I would like to fix, though I don't have time myself right now       :-(
    
    
Regards, Dave.
              
         -----Original Message-----
From: frank_lupo           [mailto:frank_lupo(at)email(dot)it] 
Sent: 09 September 2002           16:46
To: pgadmin-hackers
Subject: [pgadmin-hackers] idea !        ;  & n        bsp;for reading encodign format

      
          
for read
 ing enco
d
ign format current           version is:
          
    'Load the           Encoding Schemes
    cboProperties(0).Text =           "SQL_ASCII"
    Set objItem =           cboProperties(0).ComboItems.Add(, , "SQL_ASCII", "encoding",           "encoding")
    objItem.Selected = True
             
    cboProperties(0).ComboItems.Add , , "EUC_JP",           "encoding", "encoding"
    cboProperties(0).ComboItems.Add ,           , "EUC_CN", "e! ncoding", &        nbsp;"encoding"
              cboProperties(0).ComboItems.Add , , "EUC_KR", "encoding",           "encoding"
    cboProperties(0).ComboItems.Add , , "EUC_TW",           "encoding", "encoding"
    cboProperties(0).ComboItems.Add ,           , "UNICODE", "encoding", "encoding"
              cboProperties(0).ComboItems.Add , , "MULE_INTERNAL", "encoding",           "encoding"< BR>  ;    cboProperties(0).ComboItems.Add , ,           "LATIN1", "encoding", "encodi
 ng"
=0
A
              cboProperties(0).ComboItems.Add , , "LATIN2", "encoding",           "encoding"
    cboProperties(0).ComboItems.Add , , "LATIN3",         &nb! sp;  "        encoding", "encoding"
    cboProperties(0).ComboItems.Add ,           , "LATIN4", "encoding", "encoding"
              cboProperties(0).ComboItems.Add , , "LATIN5", "encoding",           "encoding"
    cboProperties(0).ComboItems.Add , , "KOI8",           "encoding", "encoding"
    cboProperties(0).ComboItems.Add ,           , "WIN", "encoding", "encoding"
              cboProperties(0).ComboItems.Add , , "ALT", "encoding", "encoding"
          
this version is a problem to custom           encodign into program. For new encodign modify program to add new          &n! bsp;encod i gn
          
For reading automatly encodign           usign this code : < /P>                   
Dim rsSQL As New Recordset
Dim           bIsValid As Boolean

  


  'Load the           Encoding Schemes
    bIsValid = True
    X           = 0
    While           bIsValid
        Set rsSQL =           frmMain.svr.Databases("template1").Execute("select pg_encoding_to_char(" &           X & ")")
        If          &n! bsp;rsSQL .        Fields(0).Value = "" Then bIsValid =           False
        If bIsValid           Then
            If           X = 0           Then
                          cboProperties(0).Text =           rsSQL.Fields(0).Value
                          Set objItem = cboProperties (0).Comb o Items.Add(, , rsSQL.Fields(0).Value,           "encoding",           "encoding")
                          objItem.Selected =           True
     &nbs! p; &        n bsp;              Else
                          cboProperties(0).ComboItems.Add , , rsSQL.Fields(0).Value, "encoding",           "encoding"
                      End If
        En
 d

   If
        X = X +           1
    Wend
          
 
          
bye !!
          
 
          
Frank Lupo
          


Bye !! Frank Lupo&n! bsp;(Wolf )         !!            
----
Prendi GRATIS l'email           universale che... risparmia: clicca qui           

Sponsor:
Tuffati in un mondo di occasioni d'oro...
Clicca qui 

    
               

        

        

        

      

Bye !! Frank Lupo (Wolf) !!      
----
Prendi GRATIS l'email      universale che... risparmia: clicca qui      

Sponsor:
Sei un webmaster, vuoi guadagnare? Affiliati ad      Artefiori. Clicca qui!
Clicca qui  

Bye !!
Frank Lupo (Wolf) !!


--
Prendi GRATIS l'email universale che... risparmia: http://www.email.it/f

Sponsor:
Scopri la nuovissima stampante HP. Design elegante, stampa veloce e di qualità! Scoprila qui!
Clicca qui: http://adv2.email.it/cgi-bin/foclick.cgi?mid=764&d=10-9

pgadmin-hackers by date

Next:From: Dave PageDate: 2002-09-10 18:37:56
Subject: Re: idea for reading encodign format
Previous:From: Dave PageDate: 2002-09-10 14:41:10
Subject: Re: idea for reading encodign format

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group