workarounds for ci_text - Mailing list pgsql-general

From Heine Ferreira
Subject workarounds for ci_text
Date
Msg-id CAMuqQjecF99xaZLbZ4o-bBjr6THgBM11MHqtd3+ScGZAWN29Dg@mail.gmail.com
Whole thread Raw
Responses Re: workarounds for ci_text  (Bill Moran <wmoran@potentialtech.com>)
List pgsql-general
Hi,

As far as I can tell, you can't restrict the length of a ci_text field like
char(5) or varchar(5)?
Let's say you got a stock table and you want an alphanumeric stock
code that is the primary key but it must be case insensitive can I do
something like this:

create table stock(stock code varchar(5), stock_desc varchar(50))
primary key pk_stock_code ilike(stock_code)

Will this work? Is this the right syntax?

Thanks

H.F.


pgsql-general by date:

Previous
From: Karsten Hilbert
Date:
Subject: Re: [SQL] Q: documentation bug ?
Next
From: Bill Moran
Date:
Subject: Re: workarounds for ci_text