Thread:

Theres always ERWin which works quite nicely with postgres if you use ODBC as the Target RDBMS type (and configure ODBC
datasources appropriately). 

Bryan

> -----Original Message-----
> From: frank_lupo [mailto:frank_lupo@email.it]
> Sent: 04 September 2003 07:25
> To: pgadmin-hackers
> Subject: [pgadmin-hackers]
>
>
> Hi Jean-Michel Pouré,
> this is a traslation of pgadmin3 in italian.
>

Thanks Frank - committed to CVS.

Regards, Dave.

Ah.
Sorry.
It is not multi-byte...
I go for the bed.:-)

regards,
Hiroshi Saito

From: "Hiroshi Saito" <saito@mail.skcapi.co.jp>


> From: "Andreas Pflug" <pgadmin@pse-consulting.de>
>
> > Hiroshi Saito wrote:
> (snip)
> > >It isn't understood.
> > >Shouldn't put it in SQL_ASCII.
> > >Database comes to return the result which made a mistake.
> > >Or, do you use 256(2^8=256) ASCII?
> > >
> >
> > The DB will store 8 bit per character, regardless of the db encoding.
> > When it comes to conversion, only 7 bits are valid, if you tell the
> > backend "this is ASCII data". Your fault, if it actually isn't.
>
> However,
> WHERE of SELECT will go to look for it with 7bit for ENCODING if to be SQL_ASCII.
> Then, it fails.
> And, order by, too.
> Therefore, it is the case which you must not use.
>
> regards,
> Hiroshi Saito
>