| Re: transfering all MySQL rows to an array [message #176542 is a reply to message #176540] |
Mon, 09 January 2012 12:31   |
Luuk
Messages: 329
Registered: September 2010
Karma:
|
Senior Member |
|
|
On 09-01-2012 13:24, Gregor Kofler wrote:
> Am 2012-01-09 11:27, Luuk meinte:
>> On 09-01-2012 11:09, Gregor Kofler wrote:
>>> Am 2012-01-09 10:58, Erwin Moller meinte:
>>>> On 1/9/2012 1:02 AM, Jerry Stuckle wrote:
>>>> > On 1/8/2012 6:07 PM, M. Strobel wrote:
>>>> >> Am 08.01.2012 20:04, schrieb Gregor Kofler:
>>>> >>> Am 2012-01-08 19:56, M. Strobel meinte:
>>>> >> -------cut
>>>> >>>> compiled extension in C vs. extension in PHP.
>>>> >>>
>>>> >>> I'm not aware of extensions written in PHP. You could have classes or a
>>>> >>> framework written in PHP.
>>>> >>>
>>>> >>> Gregor
>>>> >>>
>>>> >>
>>>> >> Most or all of: Mailers, Filers, AJAX, ADODB, PEAR stuff, ...
>>>> >>
>>>> >> Maybe you would not call it extension...
>>>> >>
>>>> >> /Str.
>>>> >
>>>> > No, those are not extensions.
>>>> >
>>>>
>>>> Hi Jerry and Gregor,
>>>>
>>>> I am also confused by the naming used regarding extensions used in PHP.
>>>> I know extensions you enable in php.ini are "real" extensions in the
>>>> sense that uncommenting them will add functionality to PHP (by means of
>>>> exposing the functionality in a so or dll to PHP.).
>>>> This in contrast to adding functionality WRITTEN in PHP to PHP. (Like
>>>> any function you write yourself in PHP.)
>>>>
>>>> But the word "extension" is used a lot.
>>>> For example in PEAR:
>>>> PEAR - PHP Extension and Application Repository
>>>> while all in PEAR is only PHP-code (to my knowledge).
>>>>
>>>> Just saying I can really understand Strobels confusion. :-)
>>>>
>>>> Can you shed some light on that?
>>>
>>> The manual features a list of "real" extensions:
>>>
>>> http://php.net/manual/en/extensions.php
>>>
>>>> Was PEAR maybe a misnomer?
>>>
>>> IMO: Yes.
>>>
>>> Gregor
>>
>> Interesting reading from "What is PHP's MySQL Native Driver?" on
>> http://www.php.net/manual/en/mysqli.overview.php#mysqli.overview.mysqlnd
>>
>> The mysql extension, the mysqli extension and the PDO MySQL driver *can*
>> each be individually configured to use either libmysql or mysqlnd. As
>> mysqlnd is designed specifically to be utilised in the PHP system it has
>> numerous memory and speed enhancements over libmysql. You are strongly
>> encouraged to take advantage of these improvements.
>>
>> The table at the end suggests that PDO is the future when talking about
>> PHP<-->MySQL
>
> Erm...
>
> "
> [...]
>
> Recommended by MySQL for new projects
> mysqli: Yes - preferred option
> PDO: Yes
>
> [...]
> "
>
> There's nothing wrong with PDO, but I can't see how this table proves
> your claim.
>
> Gregor
>
>
>
>
o, lol, it was not my claim, it was my understanding from looking at
that table.... (acvtive development as of PHP5.3...)
PDO cannot (yet) be the preferred option, because not all options have a
YES... ;)
--
Luuk
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]