Well, since it looks like you'd have to move to DBI anyway (which will entail rewriting some of the code...), you might also want to look at DBD::Informix which will give you a native connection to the database.

I guess this begs a larger question. Are the APIs of DBI and Win32::ODBC similar enough to do a simple replace on any Win32::ODBC calls to make them DBI calls? If you can't, then why would Win32::ODBC still be useful? I understand the history (and if you know you will never move the Perl to a non-Win32 machine, Win32::ODBC will be a better choice than DBD::ODBC), but it seems that DBI would always be the better choice in most solutions.

This is only my opinion, and I want someone to tell me if I'm wrong for thinking this way.

ALL HAIL BRAK!!!

In reply to RE: ODBC and UNIX by PsychoSpunk
in thread ODBC and UNIX by otijim

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.