On Fri, 26 Jun 1998 [EMAIL PROTECTED] wrote:
First ODBC scheme is connect - run query - get data - disconnect.
You have to get data as IO action unless you incorporate all these
scheme within unsafePerformIO call. Otherwise you will be surprised
getting data before running query.
What I am
The reason I am using Transaction rather than Connection is because I am
assuming that the database provides a transaction isolation model in which
the database is required to remain in the same state (from the point
of view of the client) until the transaction is committed. Therefore any
S. Alexander Jacobson writes:
class ODBCTransaction transaction where
odbcSelect::transaction - SQLSelect - [ODBCResult]
odbcChange::transaction - SQLChange - IO()
[...]
I am afraid that this cannot work properly.
A transaction may consist of several queries and updates. It is
On Fri, 19 Jun 1998 [EMAIL PROTECTED] wrote:
Ok, let's go to "stateless" SQL statements.
Where would you like to connect to database?
I think part of the confusion here is that I am thinking in terms of
databases with explicit support for transactions rather than Xbase and
Access databases
Haskell ODBC interface is now available on the web.
See http://members.tripod.com/~sproot/hasql.htm
I beleive I have already sent announce, but I've got no
copy of that mail from Haskell mailing list. Maybe something wrong with my mail.
Once more I admit that my code is overflooded with checking
Why can't you provide a function like
sqlSelect::ODBCTransaction - Query - ODBCResult
The function itself does unsafePerformIO and returns an ODBCResult object.
When Haskell is done using this object, it will execute the foreignObject
garbage collection callback function. The gc call back
