Please Note that this problem is caused even with an English version of
Windows.
I tried 3 different versions of PostGres (8.3.7.1 , 8.3.7.2, and 8.4) and
they all gave this same, annoying problem.
The problem is caused by using the first (default) option for the Locale
(i.e. as prompted in the
hi,
Josh Berkus wrote, On 8/9/2004 21:20:
Tom,
Well, that does deserve investigation. But I've been initdb'ing
frequently and not noticed any problems. What configure switches
did you use exactly? Did you try to move the installation tree
after configure?
Here's the issue: if you start initdb fr
hi,
Tom Lane wrote:
> =?ISO-8859-2?Q?S=FCn?= <[EMAIL PROTECTED]> writes:
>
>>If you use Latin2 encoding, you can not have 'bssz' and 'bszsz' in an
>>unique column in the same time.
>
>
> AFAICS this means that your locale definition considers these strings
> equal.
>
> It is possible that the real
hi,
PostgreSQL Bugs List wrote:
The following bug has been logged online:
Bug reference: 1112
Logged by: Ulf Mehlig
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system: Debian Linux/i386 "testing"
Description:round(float-type does not work)
D
Hi,
Sh A Guru Prasad wrote, On 12/31/2003 11:00 AM:
select trn_id,substr(hoa_id,1,13) from tbill_master where
substr(hoa
_id,1,13)='2202031040006';
trn_id |substr
+---
25001203000416 | 2202031040006
25001203000417 | 2202031040006
25001203000418 | 2202
