Eak wrote: "Do you just squirrel away SQL throughout your code?"
Depends on the scale of the project.
On large projects, there are some good arguments for hiding
all of the nitty gritty SQL behind stored procedures inside the database.
That way, should the backend database change, all well-behaved front-end apps that read and write data
through the stored procedures wont break.
On medium-size projects, I hide (encapsulate) the SQL inside
purposeful functions (eg insert_new_customer( ... ), get_all_customers( ... )
) and share these functions
across the project by putting them in a module.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.