Dan Scott wrote:
Right. And Wez posted this (partially in reply to Lester's almost
identical hysterics at that time) on this very list ages ago
(http://news.php.net/php.internals/14937 - Feb 14, 2005, to be exact):
BEGIN QUOTE:
Drivers are free(*) to implement driver specific methods on the PDO
Lester Caine wrote:
Dan Scott wrote:
Right. And Wez posted this (partially in reply to Lester's almost
identical hysterics at that time) on this very list ages ago
(http://news.php.net/php.internals/14937 - Feb 14, 2005, to be exact):
BEGIN QUOTE:
Drivers are free(*) to implement driver specifi
Larry Garfield wrote:
As a case in point, I recently tried to implement a PDO layer for Drupal as an
alternative to the mysql_* implementation. Drupal currently implements its
own prepared statements in user-space, using a printf()-like syntax and
preg_replace_callback(). When I replaced tha
Lester Caine wrote:
The main thing I see there is 'raw' SQL. Loading the variables directly
into the script, rather than simply binding them as params. I have yet
to work out a way of converting some of my dynamically generated SQL
into a format that will work with PDO - on any database. I've
Lukas Kahwe Smith wrote:
Lester Caine wrote:
Dan Scott wrote:
Right. And Wez posted this (partially in reply to Lester's almost
identical hysterics at that time) on this very list ages ago
(http://news.php.net/php.internals/14937 - Feb 14, 2005, to be exact):
BEGIN QUOTE:
Drivers are free(*) t
Following on
Lukas Kahwe Smith wrote:
Lester Caine wrote:
The main thing I see there is 'raw' SQL. Loading the variables
directly into the script, rather than simply binding them as params. I
have yet to work out a way of converting some of my dynamically
generated SQL into a format tha
Lester Caine wrote:
Following on
Lukas Kahwe Smith wrote:
Lester Caine wrote:
The main thing I see there is 'raw' SQL. Loading the variables
directly into the script, rather than simply binding them as params.
I have yet to work out a way of converting some of my dynamically
generated
Update the MySQL portions of the documentation.
Recommended by Georg Richter/Ulf Wendel/Andrey Hristov.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi!
I looked at CLI SAPI and found this code, around line 719:
#ifdef ZTS
compiler_globals = ts_resource(compiler_globals_id);
executor_globals = ts_resource(executor_globals_id);
core_globals = ts_resource(core_globals_id);
sapi_globals = ts_resource(sapi_globals
The problem here is that compiler/executor globals are allocated in
zend_startup, which is called from cli_sapi_module.startup. So what is
actually in compiler_globals and executor_globals is either tsrm_ls if
they are initialized to 0 or random crap if they aren't. Can anybody
explain me where
10 matches
Mail list logo