HP3000-L Archives

May 2000, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Mark Bixby <[log in to unmask]>
Reply To:
Mark Bixby <[log in to unmask]>
Date:
Tue, 16 May 2000 15:49:06 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
Shawn Gordon wrote:
>
> Another one that my company has started working with on our Linux projects
> is http://www.unixodbc.com/
>
> At 10:57 AM 5/16/2000, Adam Dorritie wrote:
> >Has anyone interested in ODBC looked into iODBC
> >(http://www.iodbc.org)?  It's open-source, available in ODBC 2.x
> >(stable) and 3.x (beta) flavors, ported to a variety of Unicies, and
> >licensed under the GNU LPGL (which is fairly unrestrictive).

Both of those packages only get you an ODBC driver manager, along with a bunch
of non-TurboImage drivers which doesn't do me any good.

If I had a TurboImage client driver, I could use Perl DBD::ODBC from CGI
scripts for direct access to TurboImage databases, or do similar access from
PHP.  This would be extremely cool, and would save somebody the trouble of
writing a custom TurboImage interface for Perl or PHP.

Multiple people have replied privately to me saying they've had strong needs
for their e3000 to become an ODBC client to talk to external non-e3000
databases such as Oracle or Sybase or MS SQL Server.

Seems like e3000 ODBC client capabilities would be a valuable tool for
enterprise and Internet interoperability....

- Mark B.

ATOM RSS1 RSS2