Hi everyone,
I needed to run a method after every save (I add stuff to a log table
and want the code to automatically update an RRD table too).
After unsuccessfully fiddling with column level triggers for a bit, I
realized I could just override save:
sub save {
my $self = shift;
my
> i thought
>
> get_objects( query=>{} )
> and
> %args= ( query=> {} )
> get_objects( \%args )
>
> acted the same
Why would you think that? The first example is passing a hash, the
second is passing a hashref.
--
"When I was a kid I used to pray every night for a new bike
On Feb 17, 2007, at 8:40 PM, John Siracusa wrote:
> Right, there's no ambiguity because a hashref or arrayref has never
> been a
> valid top-level arg before.
ah. ok. +1 then.
i thought
get_objects( query=>{} )
and
%args= ( query=> {} )
get_objects( \%args )
acted t
On 2/17/07 10:22 AM, Graham Barr wrote:
> On Feb 16, 2007, at 7:26 PM, Jonathan Vanasco wrote:
>> On Feb 16, 2007, at 1:11 PM, John Siracusa wrote:
>>> Con: small additional overhead to check and coerce the args
>>
>> wouldn't that require all of these get_objects parameters to now
>> become reser
On 2/16/07 9:13 PM, George Hartzell wrote:
> This question still stands, is there a standard way to use mixin
> classes w/ Loader?
The usual way is to create a common base class with all the helpers you
want, then tell the loader to use that class as the base_class.
http://search.cpan.org/dist/Ro
Hi John (and everyone),
I just figured out why I wasn't getting an automatically generated
add_ method in one of my classes. It turned out that Loader wasn't
generating the appropriate relationship.
Long story short, I had a table named "set", and another named
"set_member", one set can have ma
On Feb 16, 2007, at 7:26 PM, Jonathan Vanasco wrote:
>
> On Feb 16, 2007, at 1:11 PM, John Siracusa wrote:
>
>> Con: small additional overhead to check and coerce the args
>
> wouldn't that require all of these get_objects parameters to now
> become reserved words, unusable as column names ? ( w
On Feb 13, 2007, at 9:18 AM, John Siracusa wrote:
> On 2/13/07, Graham Barr <[EMAIL PROTECTED]> wrote:
>> This could be done by adding a column_exists method to RDBO which
>> would
>> only return true if the named column had been loaded from the DB
>> or set
>> by calling the accessor method.
