Rajesh Kumar Mallah writes:
> *1.* Suppose varchar(30) turns out to be too small oneday
> and we want to increase it to varchar(100) , what do i do ?
This is no different from the problem of changing a column type in place.
It's still being worked on.
> *2.* Its difficult to see all the con
Hi ,
I think one of the usage patterns of DOMAINS is
to have size specifications and validity constraints
at one place for easy administration of Database.
Eg, instead of declaring email to be varchar(30) in
10s of tables and putting a CHECK constraint for
presence of '@' we could dec
Peter Eisentraut wrote:
Rajesh Kumar Mallah writes:
*1.* Suppose varchar(30) turns out to be too small oneday
and we want to increase it to varchar(100) , what do i do ?
This is no different from the problem of changing a column type in place.
It's still being work
On Fri, 14 Nov 2003 23:43:26 +0530
Rajesh Kumar Mallah <[EMAIL PROTECTED]> wrote:
>
> BTW: Searching on archives.postgresql.org takes ages is it using FTS?
>
Groups.google.com has indexes of the mailing lists so you can use that
to search. I do because archives is unusably slow.
you know. we
