Joe,
The reason why I am asking is, we are building an interface layer where all our users will have a view. They shouldn't know anything about how and where the data is stored in the table. They can be seen only by the portal which will use view.
That's the reason.
Regards
skarthi
> Date: Wed, 11 Apr 2007 19:00:23 -0400
> From: dev@xxxxxxxxxxxxxxxxx
> Subject: Re: [ADMIN] [SQL] Urgent help in bit_string data type
> To: skarthi98@xxxxxxxxxxx
> CC: pgsql-admin@xxxxxxxxxxxxxx; pgsql-sql@xxxxxxxxxxxxxx
>
> Hi skarthi,
>
> On Wed, 2007-04-11 at 15:01 -0700, Karthikeyan Sundaram wrote:
> > create table test_a (b bit(3));
> >
> > create view test_vw (b1, b2, b3)
> > as select
> > to_number(substring(b,1,1)::int,'9') as b1,
> > to_number(substring(b,2,1)::int,'9') as b2,
> > to_number(substring(b,3,1)::int,'9') as b3 from test_a;
> >
> > create or replace rule test_a_ins as on insert to test_vw
> > do instead
> > insert into test_a (b) values (COALESCE(new.b1::bit,'1')||
> > COALESCE(new.b2::bit,'0')||COALESCE(new.b3::bit,'0')::bit);
> >
> > ERROR: cannot cast type numeric to bit
> >
> > How will I resolve this?
>
> *My* question is why are you doing such convoluted conversions, from bit
> string to text, then to int, etc.? It seems to me like you want to
> manipulate bits and if that's the case, you should be using the bit
> string operators, as someone pointed out a couple of days ago. In case
> you haven't looked at them, please see:
>
> http://www.postgresql.org/docs/8.2/static/functions-bitstring.html
>
> Joe
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
Live Search Maps – find all the local information you need, right when you need it. Find it!
