Download the PHP package mrmitch/mssql-bundle-legacy without Composer
On this page you can find all versions of the php package mrmitch/mssql-bundle-legacy. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download mrmitch/mssql-bundle-legacy
More information about mrmitch/mssql-bundle-legacy
Files in mrmitch/mssql-bundle-legacy
Package mssql-bundle-legacy
Short Description Microsoft SQL Server Bundle for Symfony 2+
License MIT
Informations about the package mssql-bundle-legacy
DEPRECATED
realestate.co.nz still uses this bundle, but it's in legacy code that is being phased out. The capabilities of the bundle are limited, and have been superseeded by the Doctrine SQLServer support.
If you need a Doctrine DBLib driver, something like https://packagist.org/packages/leaseweb/doctrine-pdo-dblib should work.
If you wish to continue using the library, you may fork it and maintain it yourself. There will be no further development on this bundle moving forward.
Installation
Step 1. Install MssqlBundle
Add the realestate/mssql-bundle into composer.json
"require": {
....
"realestateconz/mssql-bundle": "master-dev"
},
And run
Step 2. Configure DBAL's connection to use MssqlBundle
In config.yml, remove the "driver" param and add "driver_class" instead:
Step 3. Enable the bundle
Finally, enable the bundle in the kernel:
Notes
Prerequisites
This driver requires version 8.0 (from http://www.ubuntitis.com/?p=64) as default 4.2 version does not have UTF support
In /etc/freetds/freetds.conf, change tds version = 4.2 to tds version = 8.0
NVARCHAR & NTEXT data types
NVARCHAR & NTEXT are not supported. In SQL 2000 SP4 or newer, SQL 2005 or SQL 2008, if you do a query that returns NTEXT type data, you may encounter the following exception: _mssql.MssqlDatabaseError: SQL Server message 4004, severity 16, state 1, line 1: Unicode data in a Unicode-only collation or ntext data cannot be sent to clients using DB-Library (such as ISQL) or ODBC version 3.7 or earlier.
It means that SQL Server is unable to send Unicode data to FTREETDS, because of shortcomings of FTREETDS. You have to CAST or CONVERT the data to equivalent NVARCHAR data type, which does not exhibit this behaviour.