Author: jwage
Date: 2008-09-12 18:57:20 +0100 (Fri, 12 Sep 2008)
New Revision: 4953
Modified:
branches/1.0/docs/manual/de/improving-performance/fetch-only-what-you-need.txt
branches/1.0/docs/manual/en/improving-performance/fetch-only-what-you-need.txt
branches/1.0/docs/manual/ja/improving-performance.txt
branches/1.0/docs/manual/pt_BR/improving-performance/fetch-only-what-you-need.txt
Log:
fixes #1446
Modified:
branches/1.0/docs/manual/de/improving-performance/fetch-only-what-you-need.txt
===================================================================
---
branches/1.0/docs/manual/de/improving-performance/fetch-only-what-you-need.txt
2008-09-12 17:39:39 UTC (rev 4952)
+++
branches/1.0/docs/manual/de/improving-performance/fetch-only-what-you-need.txt
2008-09-12 17:57:20 UTC (rev 4953)
@@ -33,7 +33,7 @@
</code> Can you think of any benefit of having objects in the view instead of
arrays? You're not going to execute business
logic in the view, are you? One parameter can save you a lot of unnecessary
processing:
<code type="php">
- ... ->execute(array(1), Doctrine::FETCH_ARRAY);
+ ... ->execute(array(1), Doctrine::HYDRATE_ARRAY);
</code> This will return a bunch of nested php arrays. It could look something
like this, assuming we fetched some comments:
<code>
array(5) (
Modified:
branches/1.0/docs/manual/en/improving-performance/fetch-only-what-you-need.txt
===================================================================
---
branches/1.0/docs/manual/en/improving-performance/fetch-only-what-you-need.txt
2008-09-12 17:39:39 UTC (rev 4952)
+++
branches/1.0/docs/manual/en/improving-performance/fetch-only-what-you-need.txt
2008-09-12 17:57:20 UTC (rev 4953)
@@ -33,7 +33,7 @@
</code> Can you think of any benefit of having objects in the view instead of
arrays? You're not going to execute business
logic in the view, are you? One parameter can save you a lot of unnecessary
processing:
<code type="php">
- ... ->execute(array(1), Doctrine::FETCH_ARRAY);
+ ... ->execute(array(1), Doctrine::HYDRATE_ARRAY);
</code> This will return a bunch of nested php arrays. It could look something
like this, assuming we fetched some comments:
<code>
array(5) (
Modified: branches/1.0/docs/manual/ja/improving-performance.txt
===================================================================
(Binary files differ)
Modified:
branches/1.0/docs/manual/pt_BR/improving-performance/fetch-only-what-you-need.txt
===================================================================
---
branches/1.0/docs/manual/pt_BR/improving-performance/fetch-only-what-you-need.txt
2008-09-12 17:39:39 UTC (rev 4952)
+++
branches/1.0/docs/manual/pt_BR/improving-performance/fetch-only-what-you-need.txt
2008-09-12 17:57:20 UTC (rev 4953)
@@ -33,7 +33,7 @@
</code> Can you think of any benefit of having objects in the view instead of
arrays? You're not going to execute business
logic in the view, are you? One parameter can save you a lot of unnecessary
processing:
<code type="php">
- ... ->execute(array(1), Doctrine::FETCH_ARRAY);
+ ... ->execute(array(1), Doctrine::HYDRATE_ARRAY);
</code> This will return a bunch of nested php arrays. It could look something
like this, assuming we fetched some comments:
<code>
array(5) (
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"doctrine-svn" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.co.uk/group/doctrine-svn?hl=en-GB
-~----------~----~----~----~------~----~------~--~---
