I'm pleased to announce that the February '08 CTP for the SQL Server 2005 Driver for PHP is now available for download here. Keep in mind that this is a technology preview and is not intended for production purposes. We look forward to your feedback on the SQL Server Data Access Forum .
Please stay tuned, as we will soon be blogging about some of the new functionality in the February '08 CTP.
Program Manager, SQL Server Driver for PHP
PingBack from http://www.biosensorab.org/2008/02/19/the-february-08-ctp-is-now-available/
I have downloaded the latest CTP and yet no sqlsrv_num_rows to get the number of rows from a resultset.
This driver is still a no go for us since there are no easy way to work around sql_num_rows.
Do you think it's gonna make it into the next version?
Vu sur le blog de l'équipe du Driver SQL Server natif pour PHP : Une nouvelle pré-version - nommée CTP
Vu sur le blog de l'équipe du Driver SQL Server natif pour PHP : Une nouvelle pré-version - nommée
I tried this version and the bugs I reported earlier have been solved. I have two issues left with this driver:
- sqlsrv_num_rows (I have to use a seperate count query now)
- text limit? Is it still limited to 64k? I did not try to store/retrieve text larger yet.
Then a new bug:
- phpinfo; the table gets corrupted after the sqlsrv information.
- phpinfo; sqlsrv information does not seem to reflect the sqlsrv_configure("warnings_return_as_errors", 0); command or this command has no effect.
Other then that this version seems to work fine.
One more thing to add; I really could use a sqlsrv_data_seek; to jump immediately to a specific row in the resultset. Right now I do subsequent sqlsrv_fetch command. This is most likely slower.
To address the feedback I've recieved about num_rows, both from this blog and from other contacts, I've submitted a new post to the blog to talk about the scenario and about buffered and unbuffered resultsets.
We are not planning on adding support for buffered resultsets, which would be required in order to add a data_seek function.
- David Sceppa
can fix utf-8 bug?
i am come from china. i need insert utf-8 data to sqlserver 2005, but (February 2008) version can't work.
$tsql="update test_users set name='测试名' where uid=1";
$stmt = sqlsrv_prepare( $conn, $tsql);
$result = sqlsrv_execute( $stmt);
SQLSTATE: 42000 code: 105 message: [Microsoft][SQL Native Client][SQL Server]字符串 '娴嬭瘯鍚? where uid=1' 后的引号不完整。 SQLSTATE: 42000 code: 102 message: [Microsoft][SQL Native Client][SQL Server]'娴嬭瘯鍚? where uid=1' 附近有语法错误。 SQLSTATE: 42000 code: 8180 message: [Microsoft][SQL Native Client][SQL Server]未能准备语句。
Do you have plans to implement in this driver the PDO interface?
Regarding the question of using UTF-8 data in queries: I wouldn't recommend pushing such data into the query string, regardless of format. Your best bet is to use parameterized queries instead.
Regarding the question on implementing PDO: Based on the trends we've seen within the PHP community, we felt that creating a SQL Server Driver for PHP was a higher priority. We are looking at possibly implementing PDO in the future.