Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I just don't find SQL that hard, and if you create a neatly packaged data access layer it doesn't get in the way of building your application too much, plus you get all the benefits of writing your own code, without the frustration of having to figure out how to do that stuff in an ORM.
    • Theoretically, a good ORM provides a neatly packaged data access layer. It can certainly get in your way though if you're trying to do things that are mostly reports and don't have any use for turning the results into objects.
    • I tend to put my SQL into a package and call it from that. Neat and tidy and no SQL intermixed with my code. I am sure there are better ways of doing it and I might like some of the ORM stuff but at this point in time I haven't missed it.
      • That's exactly what I do. I've built some pretty high performance apps that way (like in the order of 10m hits/day) and it's worked well for me.