Excellent,
Thanks Hiroshi Saito, that worked a treat, I really appreciate you
posting those images. Apologies for taking up your time for something I
probably could have figured out by RTFM.
However, IMHO I still think it is a defect, in that it shouldn't really
be saving a 0 byte file sile
Hi.
Please see,
http://winpg.jp/~saito/pgAdmin/QueryTool_check/
It is necessary to set reading and writing of an option to UTF-8.
Although ANSI and UTF-8 are possible as for reading, the option
is required for writing.
Regards,
Hiroshi Saito
- Original Message -
From: "Andrew" <[EMAIL
As the attachment did not appear to make it through, the actual SQL that
causes the 0 byte save is as follows:
DROP TABLE IF EXISTS bad_data;
CREATE TABLE bad_data (
id int NOT NULL,
bad_data varchar(50) NOT NULL,
PRIMARY KEY (id)
);
INSERT INTO bad_data (id, bad_data) VALUES
(1, 'Dhabīḥah
Hi Dave,
Ignore issue 2 then if it is a known issue.
With issue 1, I have isolated two offending characters that cause the
problem: "ī" (c4ab) and "ḥ" (e1b8a5). The inclusion of either one of
them will lead to an empty file being stored. I'm using the characters
for phonetic Arabic transliter
On 07/01/2008 20:48, Bomken Basar wrote:
Now, my question is: Is there any way to check in postgres files, logs
or pgAdmin to check if the database has been upgraded or not??
To answer this question a bit more succinctly than my last essay :-)
I don't think so, because a major upgrade re
On 07/01/2008 20:48, Bomken Basar wrote:
By upgrade, i mean the upgradation of database, not the version number
increment of postgres like from 8.0 to 8.2..
If you upgrade Postgres to a new major version (IIRC this means either
of the first two parts of the version number, e.g. 8.1 -> 8.2), t
Hello sir/madam
I am university student and i am using postgres as a backend for an
application called Focalpoint.
I upgraded focalpoint but during the upgradig process from lower version to
higher version, i didn't get the page which describes about the database
upgrade.
In other installations,
Sounds good to me. This has been a bug-bear for me for a long time too.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dave Page
Sent: Monday, January 07, 2008 10:11 AM
To: Kieran McCusker
Cc: pgadmin-support@postgresql.org; [EMAIL PROTECTED]
Subject:
On 04/01/2008, Dave Page <[EMAIL PROTECTED]> wrote:
> On 04/01/2008, Kieran McCusker <[EMAIL PROTECTED]> wrote:
> > Dave
> >
> > Does Max characters per column work in 1.8.1? Whatever I set the limit does
> > not seem to affect text fields?
>
> It should do, but maybe it got broken :-(. I'll add i
On 07/01/2008, Andrew <[EMAIL PROTECTED]> wrote:
> OS: WinXP SP2
> PC: Pentium D 3 GHz, 2 GB RAM
> pgAdmin ver: 1.8.0, 1.8.1
> postgresql ver: 8.2.5-1
>
> I haven't been able to find these issues on the Internet or on the
> pgAdmin web site, so hopefully they are not duplicates of existing.
>
> Iss
10 matches
Mail list logo
