[Catalyst] Re: iterating ResultSet in controller vs. template
jgoulah at gmail.com
Thu Jun 21 15:42:24 GMT 2007
On 6/21/07, A. Pagaltzis <pagaltzis at gmx.de> wrote:
> * John Goulah <jgoulah at gmail.com> [2007-06-20 23:15]:
> > Your reading of this thread is evidently superficial since it
> > was answered several times over with _much_ more helpful
> > answers.
> It would have been a sign of superficial reading had I repeated
> everyone else's sufficient advice.
> > Sorry if I opened my ignorant mouth, but I thought it fit into
> > this list since it dealt with model, view, and controller code.
> What I said wasn't intended as a put-down, but as advice. Sorry
> if it wasn't more delicately put, but I don't know how I could
> have flower-draped it. Whether you get offended and huff or take
> it at face value and follow it is up to you; consider which
> course of action would benefit you more. I don't care either way.
> If you have further questions I and others will be glad to answer
> them, and if you decide to tell me to go to hell, well *shrug*.
> Your call.
I do appreciate any advice, though seems as if it could have been given
without the put-down. The real fact of the matter was that I didn't realize
that search returns different values based on the variable you are returning
to. And yeah I'm a bit new to perl and coming from a C background, the
"wantarray" idea on return is still a bit foreign to me.
Search docs really do help here:
Return Value: $resultset (scalar context), @row_objs (list context)
Also, maybe its just me but when I dump a ResultSet object, its very hard to
tell how to get at things. There is a ton of extra stuff in there. Perhaps
people have some ideas on easier ways to look at this object. I tried this
cookbook idea but for some reason it didn't work for me:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Catalyst