Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

Nice story, and so much to compare.

I started out with perl4.036. perl5.001m was just out and all articles I found referred to the need to upgrade, but as a company we only had dial-in internet connection which was allowed just for mail and vital system patches. So I was allowed to order the perl4 CD from a company in the US. I built perl4 for HP-UX 7 and soon after started to integrate Unify database support into it - after reading that Oracle and Sybase already managed to do so.

My colleages soon got enthousiastic, as we now did not have to write C programs anymore, but could - with some restrictions - write perl to access the databases and convert data from various sources into Unify and make quick selections into hashes. Wow, what a relief.

After perl5 got mainstream, I waited 7 years hoping someone else would write DBD::Unify, as I did see that DBI was the way forward. We kept using uniperl all those years.

Then I grabbed all existing DBD drivers and compared what approaches were available and how I could copy the work Tim and people like you did on the already existing DBD's and wrote DBD::Unify. I still maintain it, and we use it in the company every day, multiple times a day, but we are also moving away from Unify, as their support sucks and PostgreSQL has a mature relational database by now that is capable to replace Unify without losing too much functionality. Our focus really shifted over the years. In perl4 era it was just Unify. Now our main databases reach from PostgreSQL through Oracle to plain CSV files or SQLite storage.

Perl certainly enabled me to widen my database knowledge.

Enjoy, Have FUN! H.Merijn

In reply to Re: sybperl @ 20 by Tux
in thread sybperl @ 20 by mpeppler

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others contemplating the Monastery: (3)
    As of 2017-06-26 23:19 GMT
    Find Nodes?
      Voting Booth?
      How many monitors do you use while coding?

      Results (595 votes). Check out past polls.