Jodi-
Here's an example of the "hack" approach, which I've used without causing
any problems for some time:
update pg_attribute set atttypmod = 104
where attrelid = ( select oid from pg_class where relname = 'actor'
and attname = 'actor_full_name' );
In your case, you'd substitute 254 for 104, y
On Tue, 19 Aug 2003, Jodi Kanter wrote:
> I am running 7.3.3. Can I change a field that is varying character(128)
> to varying character(250)?
You can either add a column, copy the data across and drop the old column
and use rename to give the new column the old name or if you're willing
to hack
"Jodi Kanter" <[EMAIL PROTECTED]> wrote:
> I am running 7.3.3. Can I change a field that is varying character(128)
> to varying character(250)?
nope.
You can
a) create a new column named tmp of character(250).
b) copy the content from old column to new column
c) drop the old column
Title:
I am running 7.3.3. Can I change a field that is varying character(128) to
varying character(250)?
Thanks
Jodi
--
___
Jodi L Kanter
BioInformatics Database Administrator
University of Virginia
(434) 924-2846
[EMAI
On Tue, 19 Aug 2003, Rhaoni Chiu Pereira wrote:
> Hi List,
>
>
>I was wondering if someone could help me out. I'm migrating a Oracle db to
> PostgreSQL so I must rewrite the functions 'cuz the PL/pgSQL's sintax is
> different. The problem is to sum dates .. as follows:
>
> CREATE FUNCTION ft_
Hi List,
I was wondering if someone could help me out. I'm migrating a Oracle db to
PostgreSQL so I must rewrite the functions 'cuz the PL/pgSQL's sintax is
different. The problem is to sum dates .. as follows:
CREATE FUNCTION ft_vcto_dupl(NUMERIC,NUMERIC,TIMESTAMP,NUMERIC,TIMESTAMP)
RETU