Re: TEMP fields behaviour

[prev] [thread] [next] [Date index for 2005/01/14]

--- Hartmaier Alexander <Alexander.Hartmaier@xxxxxxxxx.xx> wrote:

> Hi!
> 
>  
> 
> I wanted to know the best way to do the following:
> 
>  
> 
> I need an additional column for my object NAC::Interface for a  view.
> 
> I specified the col with:
> 
> __PACKAGE__->columns(TEMP      => qw/since/);
> 
>  
> 
> I also declared this custom sql query:
> 
> __PACKAGE__->set_sql('down', 'SELECT * FROM
> nacadm.view_down_interfaces');
> 
>  
> 
> When I fetch all objects using this custom sql query the temp. col.
> 'since' isn't filled with a value although it exists in the
> 'view_down_interfaces'.
> 


others will know better than me i'm sure but since they are probably asleep
here's what i know about TEMP:

If your CLASS is_a something else (uses the is_a relationship) you can't set
TEMP cols in your CLASS (in my experience a few months ago anyway). One or the
other sets of TEMP columns trumps rather than them being merged but i can't
remember which.

Another thought is to look at the construct method code. Maybe there is
oversight in there but probably not.


=====
pjs


		
__________________________________ 
Do you Yahoo!? 
The all-new My Yahoo! - What will yours do?
http://my.yahoo.com