in reply to RE: Re: help with a Perl term
in thread help with a Perl term

Shendal, this is totally off the eval topic, but why not just stick with one flavor? I've used DBI on Win32 and UNIX, with great results (even porting from one to the other was great). Is there any specific reason why you would want to use Win32::ODBC instead of DBI? You'll have to change the connect string that creates the database handler anyway.

Just my R$0.02.

#!/home/bbq/bin/perl
# Trust no1!

Replies are listed 'Best First'.
RE: RE: RE: Re: help with a Perl term
by Shendal (Hermit) on Jun 09, 2000 at 00:15 UTC
    Using DBI was just an example. I had a script that used Win32::ODBC. I ported it over to UNIX because I wanted to add support for Oracle, not just Access databases. It was nice to add the functionality without breaking the old stuff -- or having to rewrite it.
    There are times where it would be nice to either use or not use, was my point. For example, using a package if it exists, exiting more gracefully if not. It has been an issue with some of my perl scripts (until now).
[reply]
      Ah! I'm sorry. I hadn't realized it was just an example. I'm a true DBI defender/promoter, so I think you're example just hit my soft spot for DBI. :)

      #!/home/bbq/bin/perl
      # Trust no1!
[reply]
        In retrospect, using DBI would have been better from the get-go, as it would have been more extensible and easier to change backend databases. Suffice to say that I'll use DBI next time. :-)
[reply]

In Section Seekers of Perl Wisdom