[pgadmin-support] Problems using PGAdmin III
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. func.dump Description: Binary data ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [pgadmin-support] paste ?
Alex wrote: I am using VB6/SP5 on W2K/SP3 and PgAdmin 3 ver 1.0.0 PgAdmin 3 ver 1.1.Dev (just tried it today) Problem: *Text copy from VB will not paste to PgAdmin3 Query window * It works the other way around though. Fixed in cvs, a new binary snapshot is already uploaded (20031026). 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] 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
Re: [pgadmin-support] How to use the SET data type? Help plz!
U...PostgreSQL doesn't support sets... Chris [EMAIL PROTECTED] wrote: When I add a column a table I am able to choose the SET DataType, but there is no obvious way to define the acceptable values for the set. I'd like to use the gui that I use for creating all my other columns rather than doing it by hand. The generated sql from the gui doesn't even seem right because it puts set in quotes. I can't even enter sql by hand that should add a set with values, of course my syntax might not be right as I can't seem to find a good example for creating a set. Can anyone help me in using sets with pgadmin? ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster ---(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] dump and restore in pgadmin
Does pgadmin have support for dumping and restoring a database? ---(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
[pgadmin-support] How to use the SET data type? Help plz!
When I add a column a table I am able to choose the SET DataType, but there is no obvious way to define the acceptable values for the set. I'd like to use the gui that I use for creating all my other columns rather than doing it by hand. The generated sql from the gui doesn't even seem right because it puts set in quotes. I can't even enter sql by hand that should add a set with values, of course my syntax might not be right as I can't seem to find a good example for creating a set. Can anyone help me in using sets with pgadmin? ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [pgadmin-support] How to use the SET data type? Help plz!
Odd that it is a selectable datatype in pgadmin then huh? That's a question for the pgAdmin guys, but I know that PostgreSQL has a type called 'set', which is nothing to do with sets as you understand them. If there are no sets, then is there anythign else that can be used to represent that type of data. I used them a lot in a mySQL database that I am migrating from. It is very useful to have a predefined set of values to choose from, otherwise it would just be a text field with no constraints as to the contents. It is also nice to have the popup menus of the selecable values when inputing data like how phpmyadmin handles sets. It seem slike a huge oversight to not support them. Look up CHECK constraints. Lack of 'MySQL sets' in Postgres is NOT an oversight. It's a random, non-SQL standard type that the MySQL developers made up one day that no other database on Earth supports. Why should Postgres support it? It's just a lame workaround for MySQL not supporting constraints. (Sorry to sound all worked up about it, but it's one of the things I find annoying about MySQL...) Chris ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [pgadmin-support] Problems using PGAdmin III
Hi Andreas, thank you, I'll make a try. It should eliminate the euro problem as well. -- Csaba > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of > Andreas Pflug > Sent: Sunday, October 26, 2003 7:21 PM > To: [EMAIL PROTECTED] > 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. ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
