Обсуждение: Unicode and PGAccess
Hi, I'm new here so please let me know if this is not on topic or I do anything else wrong. On my old system I used to use PGAccess to view data on a remote system. Now I get the error: Conversion from UNICODE and SQL_ASCII is not supported. I have just loaded a 7.3 version of SuSE Linux (2.4.10 kernel) to replace my 7.2 system. I am running KDE 2.2.2. When I reloaded the system I brought my old .pgaccessrc file along. I have tried taking out any references to fonts and such from it. Access the database with psql and using \set shows that the DB is indeed SQL_ASCII so the problem seems to be on my (client) side. A search of the docs shows how to set the encoding in the database, but I can find no mention of setting it on the client side. If there is such a doc, please point me to it. A search of the list archives shows only that other people have had this problem, but no real solutions other than some compile time options. I don't have the source to PGAccess so if this is what I must do, please point me to where the source may be obtained. I hope someone here can help. If you need more info, please let me know. Thanks in advance, Frank -- Frank Holt I&MT Technical Services Senior Dept. of Technical Solutions Phone : (414) 229-2982 Fax : (414) 229-6389 e-mail: frankh@uwm.edu
Frank, > I'm new here so please let me know if this is not on topic or I do > anything > else wrong. There is no "off topic" for the Novice list, unless you start talking about Oracle. ;-) > On my old system I used to use PGAccess to view data on a remote > system. Now > I get the error: > Conversion from UNICODE and SQL_ASCII is not supported. > > I have just loaded a 7.3 version of SuSE Linux (2.4.10 kernel) to > replace my > 7.2 system. I am running KDE 2.2.2. This is a universal problem with those platforms. Here's the issue in a nutshell: 1. KDE 2.2.x comes with new Tcl/tk libraries that are Unicode-native, to support more languages. 2. PGAccess, which has not been maintained for a year, was written with older libraries that are ASCII only. As a result, no character-conversion code was included in PGAccess 3. Thus, when you open PGAccess under KDE 2.2, and try to pull data from a PostgreSQL database, PGAccess tries to pull it as Unicode and will not accept ASCII. (don't ask me for techincal details. That's as much as I know) > A search of the docs shows how to set the encoding in the database, > but I can > find no mention of setting it on the client side. If there is such a > doc, > please point me to it. These are your two choices: 1. Re-compile Postges in Multibyte Encoding form. This is letting the tail wag the dog, but will solve the problem (though it may create others). 2. Use your vast knowledge of Tcl to fix PGAccess so that it converts btw. Unicode and ACSII. Personally, I'd really love to see option 2. Constantin and several others put a lot of work into PGAccess despite the almost total lack of interest from the community in the last couple of years. Having someone who could resurrect and upgrade the product would be great. > I don't > have the source to PGAccess so if this is what I must do, please > point me to > where the source may be obtained. http://www.flex.ro/pgaccess/ Jeez. There's no link to PGAccess from anywhere on the PostgreSQL home page. No wonder nobody is maintaining it! -Josh
Thanks for the prompt reply. Look's like choice 1 is going to have to do it for now, although I must admit to being intrigued by #2. It seems to me that PgAccess would more popular and thus I'm a little surprised to hear that it has not been maintained. Is there another tool that is used instead of PgAccess? Frank On Wednesday 27 February 2002 11:15 am, you wrote: > Frank, > > > I'm new here so please let me know if this is not on topic or I do > > anything > > else wrong. > > There is no "off topic" for the Novice list, unless you start talking > about Oracle. ;-) > > > On my old system I used to use PGAccess to view data on a remote > > system. Now > > I get the error: > > Conversion from UNICODE and SQL_ASCII is not supported. > > > > I have just loaded a 7.3 version of SuSE Linux (2.4.10 kernel) to > > replace my > > 7.2 system. I am running KDE 2.2.2. > > This is a universal problem with those platforms. Here's the issue in > a nutshell: > > 1. KDE 2.2.x comes with new Tcl/tk libraries that are Unicode-native, > to support more languages. > 2. PGAccess, which has not been maintained for a year, was written with > older libraries that are ASCII only. As a result, no > character-conversion code was included in PGAccess > 3. Thus, when you open PGAccess under KDE 2.2, and try to pull data > from a PostgreSQL database, PGAccess tries to pull it as Unicode and > will not accept ASCII. > (don't ask me for techincal details. That's as much as I know) > > > A search of the docs shows how to set the encoding in the database, > > but I can > > find no mention of setting it on the client side. If there is such a > > doc, > > please point me to it. > > These are your two choices: > 1. Re-compile Postges in Multibyte Encoding form. This is letting the > tail wag the dog, but will solve the problem (though it may create > others). > 2. Use your vast knowledge of Tcl to fix PGAccess so that it converts > btw. Unicode and ACSII. > > Personally, I'd really love to see option 2. Constantin and several > others put a lot of work into PGAccess despite the almost total lack > of interest from the community in the last couple of years. Having > someone who could resurrect and upgrade the product would be great. > > > I don't > > have the source to PGAccess so if this is what I must do, please > > point me to > > where the source may be obtained. > > http://www.flex.ro/pgaccess/ > > Jeez. There's no link to PGAccess from anywhere on the PostgreSQL home > page. No wonder nobody is maintaining it! > > -Josh -- Frank Holt I&MT Technical Services Senior Dept. of Technical Solutions Phone : (414) 229-2982 Fax : (414) 229-6389 e-mail: frankh@uwm.edu
Frank, > Look's like choice 1 is going to have to do it for now, although I > must admit > to being intrigued by #2. Well, if you organize something ... > It seems to me that PgAccess would more popular and thus I'm a little > > surprised to hear that it has not been maintained. Is there another > tool that > is used instead of PgAccess? Well, most of the Win32 users use pgAdminII. My guess is that *nix users don't feel a need for GUI tools. The other GUI widget for Linux/Postgres, Kpsql, also stopped being maintained over a year ago. pgPhpAdmin still works, but has very limited capabilities. Ditto for Webmin. Admittedly, after two years with Postgres, I feel less in need of a GUI tool than I once did. By the time it stopped working, I was using PgAccess just for browsing indexes, and Kpsql just so I could cut-and-paste queries from my web browser. Hopefully we'll get a new GUI management tool out of Red Hat. There's no reason to believe that they'll offer it for free, though. I'd like it if they simply took over pgAccess and finished/upgraded it, but proprietary GUI management tools and support are how one gets customers to pay $2500 for a free database. So don't hold your breath. I'd tackle the pgAccess issues myself, if I knew any tcl/tk .... -Josh