Mark Blythe (l...@markblythe.com)

While I don't use the DBIx::Class::Loader, I did notice that since the
Catalyst::Plugin::Auth refactor, that set of modules doesn't like dealing
with role_id's any longer.  I ended up creating a database view (and
corresponding DBIC class) that spits out role names rather than role IDs,
and Catalyst::Plugin::Authentication::Store::DBIx::Class liked that much
better.

This may not be the only way to solve it, but it worked for me.

Are you sure about this one?  I just tested this with DBI_TRACE, and it does
appear to use bind variables when generating the INSERT statement.  I tried
tripping it up with SQL injections, tossing in quotes, semicolons, etc, and
it always handled it gracefully, as it should when properly using binds.

Hello!

I'd like to announce a relaunch of my web site, Mister Poll, which is now
powered by Catalyst / DBIC:

http://www.misterpoll.com/

I've actually been running the site for 10 years now.  It started out as CGI
(of course) and has been mod_perl for many years now.  When I finally
decided to rewrite the blessed thing from the ground up, I chose Catalyst.
I'm quite glad I did.  For those who may be interested, it is now running on
Linux, MySQL 5.0, Catalyst, DBIC, lighttpd + FastCGI.

Many thanks to all of you on this list (and the DBIC list), who have either
helped me directly or indirectly through the archives.  My gratitude to
everybody who has contributed to produce this software as well.  It's a
great benefit to the Perl community.

Mark

Michael,

See the 'columns' attribute or the 'select / as' attribute combo.  For
example:

$schema->resultset('Foo')->search(
  {  id =3D> { -in =3D> [ 1, 2, 3 ] }  },
  {  columns =3D> [ 'id', 'title' ] }
);

It's covered in more detail in the ATTRIBUTES section of the
DBIx::Class::ResultSet perldocs.  There are also some examples in
DBIx::Class::Manual::Cookbook under 'Using specific columns'.

Good luck,
Mark

Sorry, my mistake.  I missed one change in the example.  You should
use 'select' instead of 'columns'.  At least I did:

$c->stash->{routes} = $c->model('QDB::Routes')->search(
                  {
                          'me.net_id'    => $c->stash->{net_id},
                          'me.route_beg' => $c->stash->{node_id_beg},
                          'me.route_end' => $c->stash->{node_id_end},
                  },
                  {
                          join => { 'xc_params' => 'nodes' },

                          select  => [qw/
                          me.route_id me.route_beg me.route_end
me.err_code me.comment me.net_id
                          xc_params.node_rank xc_params.ch_beg xc_params.ch_end
                          nodes.node_id nodes.node_name
                          / ],

                          as  => [qw/
                          route_id route_beg route_end err_code comment net_id
                          xc_params.node_rank xc_params.ch_beg xc_params.ch_end
                          xc_params.nodes.node_id xc_params.nodes.node_name
                          / ],

                          #TODO Paged output
                          order_by => [ @order_by ],
                          page     => $page,       # page to return
(defaults to 1)
rows => $rows, # number of results per page,
                          cache => 1
                  }
          );