Re: [INTERFACES] [pgaccess-users] RE: bugzilla.pgaccess.org

From: "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at>
To: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>, "Rod Taylor" <rbt(at)zort(dot)ca>, "Bradley Baetz" <bbaetz(at)student(dot)usyd(dot)edu(dot)au>
Cc: "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [INTERFACES] [pgaccess-users] RE: bugzilla.pgaccess.org
Date: 2002-07-11 08:32:16
Message-ID: 46C15C39FEB2C44BA555E356FBCD6FA4961E1B@m0114.s-mxs.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> > > > Changing data types probably won't appear. I don't know of anyone
> > > > working on it -- and it can be quite a complex issue to get a good
> > > > (resource friendly and transaction safe) version.
> > >
> > > I'd be happy with a non-resource friendly and non-transaction-safe version
> > > over not having the functionality at all... ;)

Certain (imho common) cases could be short circuited to only manipulate the column
definition (including default value), like alter varchar(10) to varchar(20),
or decimal(10) to decimal(20), or even varchar(10) to varchar(5) (which would need
to select all rows, and check that none is actually longer than 5, or abort).

That is what I have seen other db's do. Do it inplace where it is easily possible,
else do a long transaction that rewrites the content.

Andreas

Browse pgsql-hackers by date

  From Date Subject
Next Message Karel Zak 2002-07-11 08:38:22 Re: Proposal: CREATE CONVERSION
Previous Message Tatsuo Ishii 2002-07-11 08:26:01 Re: Proposal: CREATE CONVERSION