Problem with mixed_field in odbc_result

Zaphod_B

I use PHP 4.3.3 and MSSQL-server 7.0 and use an ODBC-connection.

My problem is that if "mixed-field" in php-function odbc_result() is more than 31 characters long.

eg.
SELECT user_id AS tbl_useruser_id FROM tbl_user
|...
$result = odbc_result($rs, 'tbl_useruser_id');

If the text marked red is over 31 characters PHP refusees to print out the sql-result.

Is this possible to fix this without:
- changing PHP version
- changing MSSQL-server-version
- changing length of the red text

konsu

per http://us3.php.net/manual/en/function.odbc-result.php you can use the column number instead of column name.

Zaphod_B

Yes... but

I want my naming standard to be "table-name"__"column-name".

Because my db contains over 500 tables and thousand of columns, if I add one column to a table the columnnumber would change and my app would "crash".

Is it php or can it be the ODBC-connection that maximize the number of chars in columnname?

Do the ODBC-connection use the DBLIB that was developed for SQL Server 6.x where the max identifier length is 30?

konsu

what error do you get from odbc_result()?
you can query the result set for the list of fields and find the index of the field with the name that you need and use this index in odbc_result

Zaphod_B

I dont get any error, the only thing is a blank result.

This is propably the answer to my question...

"Note: In Windows, the DBLIB from Microsoft is used. Functions that return a column name are based on the dbcolname() function in DBLIB. DBLIB was developed for SQL Server 6.x where the max identifier length is 30. For this reason, the maximum column length is 30 characters. On platforms where FreeTDS is used (Linux), this is not a problem."

from http://se.php.net/mssql

konsu

thanks for the information. as usual when dealing with microsoft's software one has to work around these unjustified limitations...