Go to file
Jenny Tam b47cec284b
Dev to Master - 5.4.0-preview (#853)
* Fixed the potential error reported by Prefast code analysis

* Use SQLSRV_ASSERT for checking NULL ptrs

* For these AKV tests check env despite not AE connected

* Added the driver option to run functional tests

* Fixed connection pooling tests for more than one ODBC drivers

* added driver option to pdo isPooled.php

* Removed win32 ifdefs re connection resiliency (#802)

* Set the driver argument for getDSN to null by default (#798)

* Added the driver argument to getDSN

* Dropped the driver argument but set to null as default

* Removed the AE condition in locale support

* Modified the AE condition for locale support

* Changed int to SQLLEN to avoid infinite loop (#806)

* Version 5.3.0 (#803)

* Version 5.3.0

* Fixed the wrong replacements

* Added comments block to m4 files

* Use dnl for comments

*  Modified AE fetch phptypes test to insert only one row at a time and loop through php types (#801)

* Modified AE fetch phptypes test to insert only one row at a time and loop through php types

* Fixed formatting

* Streamlined two very similar large column name tests (#807)

* Streamlined two very similar large column name tests

* Changed the EOL

* Updates to change log and readme (#811)

* Updates to change log and readme

* Dropped support for Ubuntu 17

* Modified as per review comments

* Fixed connection resiliency tests for Unix, updated AppVeyor for ODBC 17.2

* Fixed expected output

* Fixed output and skipifs

* Fixed skipifs and output

* Fixed driver name

* Updated installation instructions and sample script (#813)

* Updated instructions and sample test for 5.3.0 RTW

* Fixed sample code to adhere to php coding standard

* Fixed cases and spaces

* Modified NOTE for UB 18.04 based on review comments

* Added 'exit'

* Modified change log and readme based on review to PR 811

* Applied review comments

* build output to debug appveyor failure

* removed debug output

* Streamlined two very similar large column name tests (#815)

* Streamlined two very similar large column name tests

* Added random number of test table names to avoid operand clash issues

* Replaced to with for based on review

* Changelog updated

* changelog updated, test skipif changed to run on unix platforms

* Fixed skipif typo

* Fixed typo in skipif for pdo

* Fixed some output for Travis

* Moved error checking inside pdo connres tests

* Added links back to changelog

* Fixed output for sqlsrv connres tests

* Fixed output

* Fixed output again

* Fixed skipifs for connres

* Tweaked per review comments

* Changes made to source and tests to support PHP 7.3 (#822)

* Changes made to support php 7.3

* Correct use of the smart pointer

* Fixed the tests for 7.3

* Some clean up for array_init()

* Fixed formattings and clean up

* One more fix

* Initialising strings with nulls

* Removed some spaces

* Made array index spacing consistent

* Fix for compilation problem

* Fix for compilation problem again

* Before freeing stmt in destructor check if dbh driver data is NULL  (#829)

* Issue 434 - set dbh driver data to NULL as well in destructor

* Reverted the last change but instead check if dbh driver_data is already freed

* Modified the comment

* Added driver to the skipif conditions (#831)

* Used git clone instead to download source from a branch of a tag (#832)

* Modified the error handling to make it more flexible (#833)

* Made error handling more flexible

* Fixed a minor issue with a test

* Enabled Spectre Mitigations (#836)

* Incorporated changes in PR 634 to pdo_sqlsrv (#834)

* Incorporated changes in PR 634 to pdo_sqlsrv

* Reverted the changes because the array is for internal use only

* Modified README re user's suggestion (#841)

* Modified README re user's suggestion

* Moved the if condition to the end as per review

* Adding supporting for Azure AD access token (#837)

* Adding supporting for Azure AD access token

* Added more comments for the AD access token skipif files

* Save the pointer to access token struct until after connecting

* Clear the access token data before freeing the memory

* Added a reference as per review

* Feature request - new PDO_STMT_OPTION_FETCHES_DATETIME_TYPE flag for pdo_sqlsrv to return datetime as objects (#842)

* Feature request - issue 648

* Fixed constructor for field_cache and added another test

* Added tests for FETCH_BOUND

* Added a new test for output param

* Modified output param test to set attributes differently

* Removed a useless helped function in a test

* Combined two new tests into one as per review

* Uncommented dropTable

* Feature request - add ReturnDatesAsStrings option to statement level for sqlsrv  (#844)

* Added ReturnDatesAsStrings option to the statement level

* Added new tests for ReturnDatesAsStrings at statement level

* Added more datetime types as per review

* Updated version 5.4.0-preview (#846)

* Updated version 5.4.0-preview

* Replaced 5.3 with 5.4

* Fixed sqlsrv datetime tests to connect with ColumnEncryption variables (#849)

* Change log for 5.4.0-preview (#850)

* Updated change log for 5.4.0-preview

* Updated 5.4.0 preview to add two new feature requests

* Modified change log as per review

* Modified the wordings

* Updated readme, changelog, and install instructions
2018-09-24 13:26:43 -07:00
buildscripts Dev to Master - 5.4.0-preview (#853) 2018-09-24 13:26:43 -07:00
sample PHP 4.0.4 release 2016-05-03 20:05:41 -07:00
source Dev to Master - 5.4.0-preview (#853) 2018-09-24 13:26:43 -07:00
test Dev to Master - 5.4.0-preview (#853) 2018-09-24 13:26:43 -07:00
.travis.yml Removed support for Custom Keystore provider 2018-02-08 09:00:16 -08:00
appveyor.yml Dev (#820) 2018-07-20 17:24:48 -07:00
CHANGELOG.md Dev to Master - 5.4.0-preview (#853) 2018-09-24 13:26:43 -07:00
Dockerfile-msphpsql Reverted -- user flag not working 2018-05-02 08:43:01 -07:00
entrypoint.sh limited the loop to 10 times, max 60 sec wait 2017-08-03 13:47:56 -07:00
issue_template.md Further simplified the issue template 2018-04-20 12:29:56 -07:00
LICENSE Dev (#820) 2018-07-20 17:24:48 -07:00
Linux-mac-install.md Dev to Master - 5.4.0-preview (#853) 2018-09-24 13:26:43 -07:00
README.md Dev to Master - 5.4.0-preview (#853) 2018-09-24 13:26:43 -07:00

Microsoft Drivers for PHP for Microsoft SQL Server

Welcome to the Microsoft Drivers for PHP for Microsoft SQL Server

The Microsoft Drivers for PHP for Microsoft SQL Server are PHP extensions that allow for the reading and writing of SQL Server data from within PHP scripts. The SQLSRV extension provides a procedural interface while the PDO_SQLSRV extension implements PHP Data Objects (PDO) for accessing data in all editions of SQL Server 2008 R2 and later (including Azure SQL DB). These drivers rely on the Microsoft ODBC Driver for SQL Server to handle the low-level communication with SQL Server.

This release contains the SQLSRV and PDO_SQLSRV drivers for PHP 7.1+ with improvements on both drivers and some limitations. Upcoming releases will contain additional functionalities, bug fixes, and more.

Take our survey

Thank you for taking the time to participate in our last survey. You can continue to help us improve by letting us know how we are doing and how you use PHP by taking our December pulse survey:

Status of Most Recent Builds

AppVeyor (Windows) Travis CI (Linux) Coverage (Windows) Coverage (Linux)
av-image tv-image Coverage Codecov Coverage Coveralls

Get Started

Announcements

Please visit the blog for more announcements.

Prerequisites

For full details on the system requirements for the drivers, see the system requirements on Microsoft Docs.

On the client machine:

On the server side, Microsoft SQL Server 2008 R2 and above on Windows are supported, as are Microsoft SQL Server 2016 and above on Linux.

Building and Installing the Drivers on Windows

The drivers are distributed as pre-compiled extensions for PHP found on the releases page. They are available in thread-safe and non thread-safe versions, and in 32-bit and 64-bit versions. The source code for the drivers is also available, and you can compile them as thread safe or non-thread safe versions. The thread safety configuration of your web server will determine which version you need.

If you choose to build the drivers, you must be able to build PHP 7 without including these extensions. For help building PHP on Windows, see the official PHP website. For details on compiling the drivers, see the documentation -- an example buildscript is provided, but you can also compile the drivers manually.

To load the drivers, make sure that the driver is in your PHP extension directory and enable it in your PHP installation's php.ini file by adding extension=php_sqlsrv.dll and/or extension=php_pdo_sqlsrv.dll to it. If necessary, specify the extension directory using extension_dir, for example: extension_dir = "C:\PHP\ext". Note that the precompiled binaries have different names -- substitute accordingly in php.ini. For more details on loading the drivers, see Loading the PHP SQL Driver on Microsoft Docs.

Finally, if running PHP in a Web server, restart the Web server.

Install (UNIX)

For full instructions on installing the drivers on all supported Unix platforms, see the installation instructions on Microsoft Docs.

Sample Code

For PHP code samples, please see the sample folder or the code samples on Microsoft Docs.

Limitations and Known Issues

Please refer to Releases for the latest limitations and known issues.

Version number

The version numbers of the PHP drivers follow semantic versioning:

Given a version number MAJOR.MINOR.PATCH,

  • MAJOR version is incremented when an incompatible API change is made,
  • MINOR version is incremented when functionality is added in a backwards-compatible manner, and
  • PATCH version is incremented when backwards-compatible bug fixes are made.

The version number may have trailing pre-release version identifiers to indicate the stability and/or build metadata.

  • Pre-release version is denoted by a hyphen followed by preview or RC and may be followed by a series of dot separated identifiers. Production quality releases do not contain the pre-release version. preview has lower precedence than RC. Example of precedence: preview < preview.1 < RC < RC.1. Note that the PECL package version numbers do not have the hyphen before the pre-release version, owing to restrictions in PECL. Example of a PECL package version number: 1.2.3preview
  • Build metadata may be denoted by a plus sign followed by 4 or 5 digits, such as 1.2.3-preview+5678 or 1.2.3+5678. Build metadata does not figure into the precedence order.

Future Plans

  • Expand SQL Server 2016 feature support (example: Azure Active Directory)
  • Add more verification/fundamental tests
  • Bug fixes

Guidelines for Reporting Issues

We appreciate you taking the time to test the driver, provide feedback and report any issues. It would be extremely helpful if you:

  • First check the FAQ for common problems
  • Report each issue as a new issue (but check first if it's already been reported)
  • Please address the questions in the new issue template and provide scripts, table schema, and/or any details that may help reproduce the problem(s)

Thank you!

FAQs

Q: Can we get dates for any of the Future Plans listed above?

A: At this time, Microsoft is not able to announce dates. We are working hard to release future versions of the driver and will share future plans as appropriate.

Q: What's next?

A: On July 20, 2018 we released the production release version 5.3.0 of our PHP Driver. We will continue working on our future plans and releasing previews of upcoming releases.

Q: Is Microsoft taking pull requests for this project?

A: Yes. Please submit pull requests to the dev branch, not the master branch.

License

The Microsoft Drivers for PHP for SQL Server are licensed under the MIT license. See the LICENSE file for more details.

Code of conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Resources

Documentation: Microsoft Docs Online.

Team Blog: Browse our blog for comments and announcements from the team in the team blog.

Known Issues: Please visit the project on Github to view outstanding issues and report new ones.