mssql_guid_string
If you are performing a stored procedure inside a loop, it is a good idea to unset the variable that mssql_init returns so that you do NOT bind multiple values to the same stored procedure:
foreach($input as $sid=>$value) {
$stmt = mssql_init("sp_doSomething");
mssql_bind($stmt, "@sid", $sid, SQLINT4, false);
mssql_bind($stmt, "@value", $value, SQLINT4, false);
$result = mssql_execute($stmt);
unset($stmt); // <---VERY important
}
Even doing the mssql_init outside the loop does not help because of the multiple binds happening inside the loop.
Failing to do the above generates "Access Violations...memory cannot be 'written'" errors on the server. My hypothesis is that the error is generated when you try to bind to a stored procedure after it has already been executed. You have been warned.
mssql_init
(PHP 4 >= 4.0.7, PHP 5, PECL odbtp >= 1.1.1)
mssql_init — Initialisiert eine Stored Procedure oder eine Remote Stored Procedure
Beschreibung
resource mssql_init
( string $SP-Name
[, resource $Verbindungskennung
] )
Initialisiert eine Stored Procedure oder eine Remote Stored Procedure
Parameter-Liste
- SP-Name
-
Stored Procedure-Name wie z.B. ownew.sp_name oder otherdb.owner.sp_name.
- Verbindungskennung
-
Der von mssql_connect() zurückgegebene Bezeichner einer MS SQL-Verbindung
Rückgabewerte
Gibt den Bezeichner einer Anweisung zurück, der in nachfolgenden Aufrufen von mssql_bind() und mssql_execute() verwendet wird oder FALSE, falls ein Fehler auftrat.
Siehe auch
- mssql_bind() - Fügt einer Stored Procedure oder einer Remote Stored Procedure einen Parameter hinzu
- mssql_execute() - Führt eine Stored Procedure in einer MS SQL-Datenbank aus
- mssql_free_statement() - Gibt den Anweisungsspeicher frei
add a note
User Contributed Notesmssql_init
shrockc at NOinhs dot orgSPAM
09-Jul-2002 04:19
09-Jul-2002 04:19
fjortizATcomunetDOTes
26-Dec-2001 12:58
26-Dec-2001 12:58
this function was created to support
OUTPUT parameters and return values with
MSSQL stored procedures. Before this,
you could use T-SQL statement EXECUTE
and mssql_query to execute a stored
procedure, and it was fine as long as
you don't need to retrieve OUTPUT or
RETVAL values.
Now you can use this set of functions to execute and retrieve these values:
mssql_init
mssql_bind
mssql_execute
Parameters:
- sp_name : stored procedure name. It passes this string to a native DB-lib call, so I guess it supports all kinds of schemas (like "ownew.sp_name" or "otherdb.owner.sp_name")
- connection id: a connection resource
obtained with mssql_connect or similar.
If not provided, it will proceed just
like other similar mssql_* functions:
uses a default open connection or
creates a new one.
Return value: a resource id, called
"statement", used in subsequent calls to
mssql_bind and mssql_execute.
Note that many of the native MSSQL data types are directly supported, but I
think that some others must be converted
by other means (from varchar values for
example). These unsupported types are:
SQLMONEY4,SQLMONEY,SQLBIT,SQLDATETIM4,
SQLDATETIME, SQLDECIMAL, SQLNUMERIC,
SQLVARBINARY, SQLBINARY,SQLIMAGE
More info on supported types and new constants in mssql_bind