.TH GDI_COMMIT 3 "8/19/93 (v16.4)"
.ig
% ptroff -man gdi_commit.3
SccsID=@(#)gdi_commit.3	16.4 8/19/93
..
.SH NAME
.PP
gdi_commit \- commit current transaction
.SH SYNOPSIS
.PP
.nf
.ta 8 16
.B #include "libgdi.h"
.sp
.B int
.B gdi_commit (conn, channo)
\fBdbConn	*conn;\fP	/* (i) database conneciton */
\fBint	channo;\fP	/* (i) channel number */
\fBchar	*tran_name;\fP	/* (i) transaction name */
.fi
.sp
.SH DESCRIPTION
.PP
A database transaction is a statement, or statements, treated as an atomic unit.
gdi_commit() ends the current transaction by applying all changes to the database.
.PP
Note that SYBASE transaction management is different from INGRES and ORACLE.
.SH ARGUMENTS
.PP
.TP 12
.B conn
The database connector.
.TP 12
.B channo
The channel number for SYBASE since transactions are handled at the
DBPROCESS level, not the database connection level.
The channel argument is ignored for INGRES and ORACLE because transactions 
are at the database connection level.
.TP 12
.B tran_name
Transaction name of the transaction to be committed.  This argument is only
valid for SYBASE which allows nested, named transactions.
.SH DIAGNOSTICS
.PP
gdi_commit() returns one of the following status values:
.TP 12
.B GDI_SUCCESS
Commit succeeded.
.TP 12
.B GDI_FAILURE
Commit failed; possibly the connection dropped.
.SH FILE
.PP
gdi_tran.c
.SH NOTES
.PP
Not implemented in SYBASE or INGRES yet.
.SH SEE ALSO
.PP
.BR gdi_rollback (3),
.BR gdi_savepoint (3)
.SH AUTHOR
.PP
B. MacRitchie, SAIC Geophysical Systems Operation, Open Systems Division