If your query takes that long, maybe your forgot to create the right indizes? Did you let mysql explain the query to you?

While mysql does have some problem with optimizing subselects it's ususally not that slow.

If you use DBI you can change the database without modifying 99% of your code - just plug in a different DSN, and it uses another DBD::something backend.

If you wrote non-standard SQL you might have to fix some of that when you switch to a different DBMS.

Update: There are other ways of keeping your applications cross-platform btw. One is an ORM-Wrapper like Rose::DB::Object or DBIx::Class, another one is to use SQL::Abstract directly.

In reply to Re: advice perl and mysql by moritz
in thread advice perl and mysql by baxy77bax

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.