Re: Trouble making set_sql work...

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

From: Drew Taylor
Subject: Re: Trouble making set_sql work...
Date: 19:44 on 13 Jul 2004

Andy Harrison wrote:

> 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?

IMHO, Class::DBI is all about making the easy things dead simple and the 
hard things easier. If you can use the generated search_*() methods that 
set_sql() creates great. But you're totally fine to delve deeper down in 
to the recesses of SQL and do things that you can't (easily) do w/ C::DBI.

And as an added bonus, there are even methods that make it simple to get 
back via methods like sth_to_objects(). There is a lot of functionality 
I don't use (yet, like JOINS, etc) but it's nice to know it's there 
waiting for me.

So do what you have to do. Remember, computers don't have feelings. :-)

Drew
        -- 
        ----------------------------------------------------------------
Drew Taylor                 *  Web development & consulting
Email: drew@xxxxxxxxxx.xxx  *  Site implementation & hosting
Web  : www.drewtaylor.com   *  perl/mod_perl/DBI/mysql/postgres
----------------------------------------------------------------