Re: [pgadmin-hackers] pgAdmin 1.0.2 Bundled...
-Original Message- From: Kurt Roeckx [mailto:[EMAIL PROTECTED] Sent: 02 December 2003 23:10 To: Dave Page Cc: [EMAIL PROTECTED] Subject: Re: [pgadmin-hackers] pgAdmin 1.0.2 Bundled... On Fri, Nov 28, 2003 at 01:08:19PM -, Dave Page wrote: Hi Guys, I just finished bundling the source tarball, win32 builds and Slackware build of v1.0.2. This version is built using the new wx snapshot, which has also been added to the ftp mirrors. I find the changelog on the website rather strange. Are all the lines between v1.0.0 and v0.9.3devel what changed between 1.0.0 and 1.0.2? The dates seems to match. The header is the version to which changes were applied. E.g. V1.0.0 - Fixed fnubar widget Means that we fixed the buggy fnubar widget that was in the 1.0.0 release. Regards, Dave. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [pgadmin-hackers] Website RTL support
Le Mardi 02 Décembre 2003 18:40, Ossama Khayat a écrit : I tried that before, and now again. It gives: Connection refused. Still, if i use: psql test it logs me in. Dear Ossama, Can you send me your /var/lib/pgsql/data/pg_hba.conf and /var/lib/pgsql/data/ postgresql.conf. Then, we can discuss using instant messaging... Cheers, Jean-Michel ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [pgadmin-hackers] pgAdmin 1.0.2 Bundled...
Dave Page wrote: Agreed, it is a little confusing. Suggestions for improvements anyone? Regards, Dave. CHANGELOG.txt could look like this, without release headers: li2003-12-03 AP *** fix connect to MULE_INTERNAL db li2003-12-02 AP fix acl property display li2003-12-02 AP another fix closing Query Tool li2003-12-01 AP add display of superuser context settings li2003-11-30 AP handle covering index for Foreign Keys li2003-11-30 AP fix closing Query Tool while query is running li2003-11-30 AP fix error message when SET client_encoding fails li2003-11-26 AP 1.0.2 fix notice processing for pgQueryThread li2003-11-24 AP refactoring stats/depends: populate on demand --^ denotes the release version, or *** if this patch is going to trunk also. Maybe we need release notes too, extracting all lines for released versions. Regards, Andreas ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [pgadmin-hackers] Error message while connecting to a UNICODE
Andreas Pflug wrote: MULE_INTERNAL-UNICODE not possible, I thought *every* server encoding could be read with client_encoding unicode... Just checked, there's no conversion indeed. What the heck is that at all? I didn't find *any* site that's not referencing pgsql when searching for MULE_INTERNAL. Fixed: pgAdmin3 won't try to use Unicode if server encoding is MULE_INTERNAL. Raphael, since you're using this encoding, what is it good for? Regards, Andreas ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [pgadmin-hackers] Error message while connecting to a UNICODE
Andreas Pflug wrote: Andreas Pflug wrote: MULE_INTERNAL-UNICODE not possible, I thought *every* server encoding could be read with client_encoding unicode... Just checked, there's no conversion indeed. What the heck is that at all? I didn't find *any* site that's not referencing pgsql when searching for MULE_INTERNAL. Fixed: pgAdmin3 won't try to use Unicode if server encoding is MULE_INTERNAL. Raphael, since you're using this encoding, what is it good for? In fact I thought I was not. I'm sorry I don't know anything about MULE_INTERNAL... (this is a real admittance of total ignorance from myself... It looks like it has something to do with what is used in emacs [a friend of you as far as I remember]). In fact I configured my db to set UNICODE by default and thought it was the one used. I'll have a look to the config file generated by the postgresql debian package debconf forms and try to overlook where this MULE_INTERNAL reference comes from... Hope you were not too disappointed by lack of knowledge... Regards, Raphaël ---(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-hackers] Error message while connecting to a UNICODE
Raphaël Enrici wrote: In fact I thought I was not. I'm sorry I don't know anything about MULE_INTERNAL... (this is a real admittance of total ignorance from myself... It looks like it has something to do with what is used in emacs [a friend of you as far as I remember]). In fact I configured my db to set UNICODE by default and thought it was the one used. I'll have a look to the config file generated by the postgresql debian package debconf forms and try to overlook where this MULE_INTERNAL reference comes from... Hope you were not too disappointed by lack of knowledge... Deeply! :-) Well, if it's an EMACS mode, I should consider switching to MULE_INTERNAL... Regards, Andreas ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [pgadmin-hackers] Error message while connecting to a UNICODE
Andreas Pflug wrote: Raphaël Enrici wrote: In fact I thought I was not. I'm sorry I don't know anything about MULE_INTERNAL... (this is a real admittance of total ignorance from myself... It looks like it has something to do with what is used in emacs [a friend of you as far as I remember]). In fact I configured my db to set UNICODE by default and thought it was the one used. I'll have a look to the config file generated by the postgresql debian package debconf forms and try to overlook where this MULE_INTERNAL reference comes from... Hope you were not too disappointed by lack of knowledge... Deeply! :-) Shame on me! :) Well, if it's an EMACS mode, I should consider switching to MULE_INTERNAL... That's what I was suggesting :) I can't understand you didn't see it! ;p I just had a quick look to template1 and it is effectively in MULE_INTERNAL. I think this is the rest of some testing I did about 3 or 4 weeks ago... I didn't clear my environment after that. That's why template1 is in EMULE_INTERNAL... Regards, Raphaël aka MULE_INTERNAL ---(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-hackers] Error message while connecting to a UNICODE
Raphaël Enrici wrote: Hope you were not too disappointed by lack of knowledge... Deeply! :-) Shame on me! :) Well, I'm considering forgiving you. This time... Regards, Raphaël aka MULE_INTERNAL At least mule, not donkey :-) Regards, Andreas ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
