Re: Trouble making set_sql work...

[prev] [thread] [next] [Date index for 2004/07/13]

On Tue, 13 Jul 2004 19:38:06 +0100, colm-cdbi@xxxxxxxxx.xx.xx
<colm-cdbi@xxxxxxxxx.xx.xx> wrote:
> 
> I wouldn't recommend doing it that way.
> 
> In the spirit of Class::DBI IMO it would be best to wrap a method around
> the auto-generated sql_show_top.
> 
> Your SQL implies you want raw data and not objects.  If so I haven't
> tried it but this should be mostly right :
> 
>  __PACKAGE__->set_sql( show_top => q{
>              SELECT option_data, COUNT(*)
>              FROM entry_options
>              WHERE option = ?
>              GROUP BY option_data
>              ORDER BY count DESC
>              LIMIT %s
>          });
> 
>   sub get_top_matches {
>     my ($self, $option, $limit) = @_;
>     my $sth = $self->sql_show_top($limit);
>     $sth->execute($option);
>     return $sth->fetchall_arrayref();
>   }
> 
>   # in a nearby script :
> 
>   my $top_matches = Your::Class->get_top_matches($option, $limit);
>   foreach my $result ( @$top_matches ) {
>     my ($option_data, $count) = @$result;
>     printf("%5d => %s\n", $count, $option_data);
>   }


Got that working, thanx.

But doesn't having to do the set_sql go against the spirit of
Class::DBI anyway?  What's the proper thing to do in a situation like
this where you might have to make a proprietary sql statement to get
the results you need?


        -- 
        Andy Harrison