[SQL] force view column varchar(32) to varchar(128)
Hello, Is there a way to force the view column change from varhcar(32) to varchar(128)? Example: === v1 (id varchar(32) ... ) There are more than 1000 other views depend on v1. Instead of recreating all other 1000 views, is there a way postgresql 8.3 can do/accept: create or replace v1 AS select id::varchar(128), .. Thanks a lot! -- Lu Ying -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql
Re: [SQL] force view column varchar(32) to varchar(128)
Emi Lu wrote: > Hello, > > Is there a way to force the view column change from varhcar(32) to > varchar(128)? No, you have to recreate the view ... Andreas -- Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect. (Linus Torvalds) "If I was god, I would recompile penguin with --enable-fly." (unknown) Kaufbach, Saxony, Germany, Europe. N 51.05082°, E 13.56889° -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql
Re: [SQL] force view column varchar(32) to varchar(128)
On Fri, Nov 19, 2010 at 7:02 AM, Emi Lu wrote: > Is there a way to force the view column change from varhcar(32) to > varchar(128)? > Instead of recreating all other 1000 views, is there a way postgresql 8.3 > can do/accept: Ouch! That stinks. I feel your pain (well my pain came from just changing about 15-20 views. changing 1000 views would make me cringe). Its too bad you haven't or can't use a dimensionless varchar for your id column (I assume this is your primary key). This would eliminate the need to re-dimension your varchar columns. As I see it, you don't have an option. PgAdmin can be a great help here. Open the create script and make the changes and save both. The only other Option that I can see would be to dump the table and view defintions. Modify these definitions with sed. Apply the new schema, and lastly, use an ETL software to push your data to the new schema. -- Regards, Richard Broersma Jr. Visit the Los Angeles PostgreSQL Users Group (LAPUG) http://pugs.postgresql.org/lapug -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql
