I just spent a few hours trying to get ntext data with this function, CASTing and CONVERTing every which way, and scouring the 'net. Nothing worked, I just got a NULL.
Then on a whim I tried it with mssql_fetch_row instead, and that DOES work.
mssql_fetch_array
(PHP 4, PHP 5, PECL odbtp:1.1.1-1.1.4)
mssql_fetch_array — Captura la fila en un array
Descripción
int mssql_fetch_array
( int $result
)
Devuelve: Un array que corresponde a la fila capturada, o FALSE si no hay más filas.
mssql_fetch_array() es una versión extendida de mssql_fetch_row(). A¤ade el almacenar los datos en los índices numéricos del array resultante, también almacena los datos en índices asociativos, usando los nombres de los campos como claves.
Una observación a tener en cuenta es, que usar mssql_fetch_array() NO es más lento que usar mssql_fetch_row(), mientras que esta provee un valor a¤adido significativo.
Para más detalles, ver también mssql_fetch_row()
mssql_fetch_array
php at bricology dot com
18-Jul-2008 06:08
18-Jul-2008 06:08
blood - demon at gmx dot net
17-Aug-2007 11:22
17-Aug-2007 11:22
Note that if you fetch varchar fields larger than 255 letters the result will be cut off at 255 letters.
To prevent this you have to do a CONVERT(TEXT,data_field) for this fields in your select clause.
Bryan
05-Jul-2007 06:05
05-Jul-2007 06:05
Calling this function with the option second parameter is causing a "Wrong parameter count" message. If you run into this problem, you can get the same effect by calling different functions:
mssql_fetch_array: MSSQL_BOTH
mssql_fetch_assoc: MSSQL_ASSOC
mssql_fetch_row: MSSQL_NUM
admin at talente dot ro
19-Oct-2005 05:36
19-Oct-2005 05:36
There is any option like skip or go next ! I am using a while clause inside:
While ($row=mysql_fetch_array($result))
while ($row["Brand_name"]=$gr){
....
So I am printing different TD from classes and when I finish cycling the fields I want to "skip" to next record !
gillis dot phpmanual at no-spam-for-megillis dot fi
06-Jul-2005 10:19
06-Jul-2005 10:19
Allthough probably obvious to people who have used the functions available to other databases it during writing is not present in this entry that result type can be entered as MSSQL_ASSOC or MSSQL_NUM, and the default value when nothing entered being MSSQL_BOTH
//Gillis Danielsen
archwisp at gmail dot com
26-Oct-2004 04:44
26-Oct-2004 04:44
In response to my last post:
After further testing, it appears as though the null column bug only affects windows installations. On my linux installation using freetds-0.61.2, the function behaves properly. It must exist either in the php_mssql.dll or the Microsoft connection libraries. And since I use this functionality through ASP as well (which uses the Microsoft connection libraries), it would lead me to believe that it's an issue within the php_mssql.dll.
archwisp at gmail dot com
25-Oct-2004 11:28
25-Oct-2004 11:28
[Editor's Note: NULLs *are* distinguishable from 0. See the manual section on comparison operators. ]
microsoft sql 2000 server
php running on windows 2000
Using the $row = mssql_fetch_array($result)
A null value will return 0, this is a problem if you are using 0 and some identifier for a value. you should convert all nulls to something like -1 or "NO VALUE"
******
After extensive testing, the above statements both seem to be true. You *can* distinguish between 0 and null values in PHP; however, the mssql_fetch_array function does not set null colums to the php NULL value.
if ($row['Null_Column'] === 0) { print('pass'); }
A null column passes the above test. Seems to be a bug in the function.
Derek Ethier
25-Feb-2004 12:06
25-Feb-2004 12:06
The array_walk function is also useful for stripping the whitespace returned in an mssql_query.
function modify_field(&$array) {
$array = trim($array);
}
$query = "select * from dbo.table where value = '0'";
$result = mssql_query($query) or die;
while ($row = mssql_fetch_array($result)) {
// This will call the above function.
array_walk($row, 'modify_field');
array_push($eventresults, $row);
}
An added benefit is that you can expand the modify_field function to handled unexpected returned column data.
hackajar matt yahoo trot com
24-Jan-2004 12:11
24-Jan-2004 12:11
from php-dev mailing list article -
#26012 [Bgs]: mssql_fetch_array
"Previously mssql data was always rtrimed, however that's wrong because it modifies the original data. This caused a problem for people who needed those trailing space. Ultimately, the job of database extension is to fetch the data as is (like other db extensions already do) and not to mangle it in any way."
moving from <4.3.4 to a higher version you will have this now:
$query = "Select dumb_spaces from dbo.table where weak_sause = 'true'";
$result = mssql_query($query) or die("Spicy Sause! Query = $query");
while($line = mssql_fetch_array($result, MSSQL_ASSOC) {
foreach($line as $bs_trim) {
//Trim whitespace from end of query
$bs_trim = rtrim($bs_trim);
echo "Clean!".$bs_trim;
}
}
herriedm at yahoo dot com
25-Jun-2003 06:21
25-Jun-2003 06:21
[Editor's Note: NULLs *are* distinguishable from 0. See the manual section on comparison operators. ]
microsoft sql 2000 server
php running on windows 2000
Using the $row = mssql_fetch_array($result)
A null value will return 0, this is a problem if you are using 0 and some identifier for a value. you should convert all nulls to something like -1 or "NO VALUE"
flatcable2000 at yahoo dot com
15-Jan-2003 06:22
15-Jan-2003 06:22
Apparently php 4.0.6 does not support the second parameter. When used the error sounds
"Wrong parameter count for mssql_fetch_array"
shaver at qspeed dot com
10-Jan-2003 11:08
10-Jan-2003 11:08
Note that the second parameter is the same as the msql version of this function (http://www.php.net/manual/en/function.msql-fetch-array.php) with the constants (MSQL_ASSOC, MSQL_NUM, and MSQL_BOTH) changing to MSSQL_.
Also note that if you don't specify this parameter you'll get both the numbers and column names, which can cause some frustration.
ask at manniac dot de
05-Jun-2002 03:13
05-Jun-2002 03:13
It seems that this function creates arrays wich keys can not be longer than 30 chars. So when you're having a DB-field like "this_is_a_very_long_db_field_name"
its array-key is cut off after 30 chars and you will have to access the value with
rs["this_is_a_very_long_db_field_n"]
