I think your real challenge will lie not is making it cross database, but in keeping the performance up to snuff and doing that at the same time. Most people think in terms of feature issues when they think of porting, but as a performance analyst of sorts I see the other side of the coin. When I work with some of these e-application platforms and ERP (Vignette, BEA, PeopleSoft, SAP, etc.), they all put high value on their DB independence. But every one of them pays a price on the performance side. Either they have huge routines to go through to optimize for each DB and then do checks to see which one it is; or they end up writing such generic SQL that it does not take advantage of any of the optimizations that these DBs make available in order to perform really well.

The moral here is to be aware of performance considerations as you go forward and try and be DB independent. Remember too that people will bend from need and if what you're doing provides enough value to them, they will support the DB you design and optimize for because they need what you are doing. 

"A man's maturity -- consists in having found again the
seriousness one had as a child, at play."   --Nietzsche

[download]

In reply to (jptxs) Re: Cross platform commonality with the Perl DBI by jptxs
in thread Cross platform commonality with the Perl DBI by cLive ;-)

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.