Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:25053
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <44CB8BB8.7090202@hauser-wenz.de>
Date: Sat, 29 Jul 2006 09:24:24 -0700
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To:  internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [PHP-DEV] RE: CVS Account Request: cleong
From: chw@hauser-wenz.de (Christian Wenz)

Hi Andi,

ASP.NET is using OLEDB, as well, and in my experiences this does not add 
to much penalty to communicating with MSSQL (however obviously more 
exhaustive performance tests are required). However I am wondering 
whether the OLEDB way would still work on non-Windows PHP versions? If 
not: Having two compatible, but internally completely different MSSQL 
extensions for win32 and non-win32 sounds dangerous to me.

--Christian

> Hi Chung,
>
> Any idea on the performance of OLEDB? My understanding was that due to it
> going through the COM layer, performance will be relatively poor.
>
> Any idea?
>
> Andi 
>
> > -----Original Message-----
> > From: Chung Leong [mailto:chernyshevsky@hotmail.com] <mailto:chernyshevsky@hotmail.com%5D> 
> > Sent: Friday, July 28, 2006 2:37 PM
> > To: internals@lists.php.net
> > Subject: [PHP-DEV] CVS Account Request: cleong
> > 
> > I would like to submit a replacement for the Win32 mssql 
> > extension that I have recently completed. The extension 
> > provides the same set of functions as mssql, but uses OLEDB 
> > to talk to SQLServer instead of DBLIB. It allows users to 
> > retrieve varchar column wider than 255 and also Unicode 
> > columns as UTF-8.
> >