The quoting may confuse an editor (it does confuse the perl.vim code).

First, and most important, you should use placeholders instead of inserting Perl variables directly into SQL. Your code will break, for example, if HTTP_USER_AGENT or HTTP_REFERER contain an apostrophe (both of these values are under user control). Serious security risks can occur if you ignore this issue. For info, google SQL injection.

As a minor matter, you can avoid quoting literal hash keys if they are made up of all word characters (i.e. match /^\w+$/). For example, you can say <code>$Session->{idSession}. I see you did that one place.

In reply to Re: code snippet by Thelonius
in thread code snippet by grashoper

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.