Hi Hiroshi, Andreas said he'd already fixed it so I didn't apply your patch. I can see the fix in both branches.
Regards, Dave. > -----Original Message----- > From: Hiroshi Saito [mailto:[EMAIL PROTECTED] > Sent: 04 October 2003 02:04 > To: Alexandr S; Andreas Pflug > Cc: Dave Page; [EMAIL PROTECTED] > Subject: Re: [pgadmin-support] [BUGS] bug reporting > > > Hi Andreas. > > I take the report that it looks like this in Japan. > It was a problem with Windows. > There is patch which I suggested before. > It is important though this was ignored. > See it again. > > OT) > My server is in bad condition, and I haven't been able to > talk well since yesterday. :-( > > regards, > Hiroshi Saito > > From: "Andreas Pflug" <[EMAIL PROTECTED]> > > > > Alexandr S wrote: > > > > > Pgadmin 3.1 don t work (operations like insert rows) with columns > > > named in russian language (title of column in russian > language). But > > > the same operations using PhpPgAdmin - all works very > well, right. > > > And if replace russian title of column with equivalent in > english - > > > all works very well. PgAdmin responds the message: "2003-10-03 > > > 14:15:15 ERROR : Column not found in pgSet: еще_колонка". > > > Operation > > > System: Windows XP, distribution binary (zip), language russian. > > > > > Hi Alexandr, > > > > you're on the wrong list, please use pgadmin-support for pgAdmin > > related questions. > > > > Which tool did you use to insert the data? > > > > Regards, > > Andreas > ---------------------------(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
