Hi people!

Hmmm... I think that such package must support the concepts:

- a connection
- a statement
- some form of resultset

That is the base of JDBC (in Java), or System.Data (in .NET). In those
worlds, this concepts are interfaces, and there are distinct providers for
concrete implementations.

The first implementations can be any driver that use sockets and propietary
protocol to communicate to a database server (like MySql clients on Java,
see www.mysql.com, or MS SQL Server using TDS, see www.freetds.org)

Angel "Java" Lopez
http://www.ajlopez.com/

----- Original Message ----- 
From: "Kamil Kukura" <kamk at volny.cz>
To: "The general-purpose Squeak developers list"
<squeak-dev at lists.squeakfoundation.org>
Sent: Thursday, August 05, 2004 12:04 PM
Subject: squeak to meet databases


> Hi,
>
> I would like to first point out that I don't intent to compare here
> databases like relational vs. object ones. It's all about getting squeak
> and ubiquitous world of relational databases together.
>
> When trying to attract web developers from environments such as PHP, ASP
> or JSP, I'm badly missing a thing to show as how Squeak deals with
> external databases. Perhaps best way to connect to any DB is to use ODBC
> which scares me as it relies on FFI
> <http://minnow.cc.gatech.edu/squeak/2424>
> .NET people have ADO, Perl/Ruby builds on DBI, Javists rely on JDBC, "C"
> hard workers stick to ODBC and PHPers go almost native though they also
> have something: http://adodb.sourceforge.net/
>
> So I'm thinking what would be nice to have to show up with more
> databases Squeak can natively talk to. Right now I consider to do some
> work on "SqDBC". At first, it would be a package containing ODBC and
> ODBCEnh as its default database driver. Then I would like to "grow up"
> PostgreSQL package in the way it would become SqDBC driver (and upgrade
> it to protocol 3 as well). Then add some connection pooling to SqDBC.
> I know it looks quite "javish" as their JDBC but I don't know if is
> there better "natural" approach.
>
> -- 
> Kamil Kukura
>