Re: Problem with mssql_query()

I dunno 100% for sure about MSsql, but I know for sure that MySQL lets you do wording_id = '8' when wording_id is an INT and PostgreSQL will simply throw an error, because '8' is not no way no how an INT. It's a string. I suspect MS SQL may be doing the same, in its own unique bland non-desript way of just saying "error"... Try losing the '8' and use just 8 On Wed, May 9, 2007 8:57 am, Chris Boget wrote: > I noticed the following in my logs: > > 22:04:42 [warning] [D:\PHP\pear\DB\mssql.php][439]: mssql_query(): > Unable > to set query > 22:04:42 [info] Backtrace: [D:\PHP\pear\DB\mssql.php][439]; > function( > mssql_query ); args( 1[value:select @@ERROR as ErrorCode] > 2[value:Resource > id #21] ) > 22:04:42 [info] Backtrace: [D:\PHP\pear\DB\mssql.php][489]; > function( > errornative ) > 22:04:42 [info] Backtrace: [D:\PHP\pear\DB\mssql.php][145]; > function( > mssqlraiseerror ) > 22:04:42 [info] Backtrace: [D:\PHP\pear\DB\common.php][1146]; > function( > simplequery ); args( 1[value:SELECT * FROM wording WHERE wording_id = > '8' ] ) > 22:04:42 [critical] Error in the following query:<br><br>SELECT * > FROM > wording WHERE wording_id = '8' <br>DB Error: unknown error > 22:04:52 [warning] [D:\PHP\pear\DB\mssql.php][439]: mssql_query(): > Unable > to set query > 22:04:52 [info] Backtrace: [D:\PHP\pear\DB\mssql.php][439]; > function( > mssql_query ); args( 1[value:select @@ERROR as ErrorCode] > 2[value:Resource > id #21] ) > 22:04:52 [info] Backtrace: [D:\PHP\pear\DB\mssql.php][489]; > function( > errornative ) > 22:04:52 [info] Backtrace: [D:\PHP\pear\DB\mssql.php][145]; > function( > mssqlraiseerror ) > 22:04:52 [info] Backtrace: [D:\PHP\pear\DB\common.php][1146]; > function( > simplequery ); args( 1[value:SELECT * FROM wording WHERE wording_id = > '8' ] ) > 22:04:52 [critical] Error in the following query:<br><br>SELECT * > FROM > wording WHERE wording_id = '8' <br>DB Error: unknown error > > Why is mssql_query() saying that it's unable to set the query? I did > some > searching on Google and found that people were having this problem but > that > was back in 2001 using an earlier version of PHP. We are using > version > 4.3.11 and Microsoft SQL Server 2000 - 8.00.2039 (Intel X86). > > Has anyone had a similar problem? What was your solution? Why is > this > happening? > > thnx, > Chris > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some indie artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So?