From f02cae8214b1a64049bcd5b8cf41a848e503cd2c Mon Sep 17 00:00:00 2001 From: zYne Date: Sat, 11 Nov 2006 20:15:08 +0000 Subject: [PATCH] --- ...ents - Eventlisteners - List of events.php | 24 ++++++------- ...omponents - DB - Using event listeners.php | 36 ------------------- ...ponents - Query - DQL - SQL conversion.php | 31 ---------------- manual/documentation.php | 7 ++-- 4 files changed, 16 insertions(+), 82 deletions(-) delete mode 100644 manual/codes/Basic Components - DB - Using event listeners.php diff --git a/manual/codes/Advanced components - Eventlisteners - List of events.php b/manual/codes/Advanced components - Eventlisteners - List of events.php index 930017e73..b8ade15ed 100644 --- a/manual/codes/Advanced components - Eventlisteners - List of events.php +++ b/manual/codes/Advanced components - Eventlisteners - List of events.php @@ -1,5 +1,6 @@ diff --git a/manual/codes/Basic Components - DB - Using event listeners.php b/manual/codes/Basic Components - DB - Using event listeners.php deleted file mode 100644 index 43ef6a141..000000000 --- a/manual/codes/Basic Components - DB - Using event listeners.php +++ /dev/null @@ -1,36 +0,0 @@ -getQuery(); - } -} - -$dbh->setListener(new MyLogger()); - -$dbh->query("SELECT * FROM foo"); -// prints: -// database is going to be queried -// executed: SELECT * FROM foo - - -class MyLogger2 extends Doctrine_Overloadable { - public function __call($m, $a) { - print $m." called!"; - } -} - -$dbh->setListener(new MyLogger2()); - -$dbh->exec("DELETE FROM foo"); -// prints: -// onPreExec called! -// onExec called! -?> diff --git a/manual/docs/Basic Components - Query - DQL - SQL conversion.php b/manual/docs/Basic Components - Query - DQL - SQL conversion.php index 3abe47a33..89a69c7a2 100644 --- a/manual/docs/Basic Components - Query - DQL - SQL conversion.php +++ b/manual/docs/Basic Components - Query - DQL - SQL conversion.php @@ -53,34 +53,3 @@ foreach($e as $line) { } renderQueries($str); ?> -Propably the most complex feature DQL parser has to offer is its LIMIT clause parser. In pure -sql the limit clause limits the number of rows returned. So for example when fetching users and their -phonenumbers using limit 20 you might get anything between 1-20 users, since the first user might have 20 phonenumbers and -hence the record set would consist of 20 rows. -

-DQL overcomes this problem with subqueries and with complex but efficient subquery analysis. In the next example -we are going to fetch first 20 users and all their phonenumbers with single efficient query. Notice how the DQL parser is smart enough -to use column aggregation inheritance even in the subquery. -

- -In the next example -we are going to fetch first 20 users and all their phonenumbers and only those users that actually have phonenumbers (hence the usage of colon operator = INNER JOIN) with single efficient query. -Notice how the DQL parser is smart enough to use the INNER JOIN in the subquery. -
- - - diff --git a/manual/documentation.php b/manual/documentation.php index e1f8c7fd0..58ffaf6fd 100644 --- a/manual/documentation.php +++ b/manual/documentation.php @@ -394,6 +394,7 @@ $menu = array("Getting started" => ), ), */ + /** "Improving performance" => array( "Introduction", "Data types" => @@ -434,7 +435,7 @@ $menu = array("Getting started" => "Performance monitoring" => array( "Using the database profiler") ), - + */ "Technology" => array( "Architecture", "Design patterns used", @@ -535,7 +536,7 @@ $menu = array("Getting started" => } $e = implode(".",array($i,$i2,$i3)); - print "
".$e." ".$v2."$str
\n"; + print "
".$e." ".$v2."
\n"; $i3++; } print ""; @@ -552,7 +553,7 @@ $menu = array("Getting started" => $str .= " [ code ] "; //touch("codes/$title - $t.php"); } - print "
".$e." ".$t."$str
\n"; + print "
".$e." ".$t."
\n"; } $i2++;