I create a new database use UTF-8 and SQL_ASCII, same result found, how
can i fix this problem ?
CK
Kevin Grittner wrote:
CK Leung wrote:
the result : select * from tt order by item_code;
item_code
--
V
.V
V.
VA.AAA
V.B
V
(V
CK Leung wrote:
> I create a new database use UTF-8 and SQL_ASCII, same result found, how
> can i fix this problem ?
If I recall correctly, the collation order is set at initdb time, and
isn't bound to the database encoding. If that's right, you'd need to
dump all your databases, re-initdb with th
Try setting the variable lc_collate, either in an individual session
using SET or (to change it for all session) in postgresql.conf.
Craig Ringer wrote:
CK Leung wrote:
I create a new database use UTF-8 and SQL_ASCII, same result found, how
can i fix this problem ?
If
The following bug has been logged online:
Bug reference: 4790
Logged by: Piergiorgio Buongiovanni
Email address: p.buongiova...@net-international.com
PostgreSQL version: 8.3
Operating system: Server Linux and client Windows
Description:ENUM word not recognized!
Detail
Piergiorgio Buongiovanni wrote:
> I'm using Query Tool of pgAdmin III and trying to execute this:
>
> CREATE TYPE business.EuropeanCEFLevel AS ENUM
> ('A1','A2','B1','B2','C1','C2');
>
> but the following error is raised:
>
> ERROR: syntax error at or near "ENUM"
> LINE 1: CREATE TYPE "busines
On Sat, May 2, 2009 at 9:15 PM, Kevin Field wrote:
> Okay, I uninstalled both 5.8 and 5.10, installed 5.10 fresh, and it
> doesn't detect it during install. I tried another fresh install of
> 5.10 with PerlScript. Same deal. Now I'm trying a fresh install with
> all options checked. Still no
