Nathan Rixham wrote:
For fixed pages this is the best way of handling the information. And
handling those fixed pages is ... from my point of view ... not a
problem since they can be cached at that level, or even stored locally
in the browser cache. I've just been hitting re-load every time for a
> -Original Message-
> From: Tommy Pham [mailto:tommy...@gmail.com]
> Sent: Sunday, December 12, 2010 12:53 PM
> To: 'nrix...@gmail.com'
> Cc: 'Peter Lind'; 'php-general@lists.php.net'; 'Lester Caine'
> Subject: RE: [PHP] ORM d
> -Original Message-
> From: Nathan Rixham [mailto:nrix...@gmail.com]
> Sent: Sunday, December 12, 2010 11:41 AM
> To: Tommy Pham
> Cc: 'Peter Lind'; php-general@lists.php.net; 'Lester Caine'
> Subject: Re: [PHP] ORM doctrine
>
> Tommy Pham wrot
Tommy Pham wrote:
-Original Message-
From: Nathan Rixham [mailto:nrix...@gmail.com]
Sent: Sunday, December 12, 2010 8:23 AM
To: Tommy Pham
Cc: 'Peter Lind'; php-general@lists.php.net; 'Lester Caine'
Subject: Re: [PHP] ORM doctrine
Tommy Pham wrote:
-Origin
> -Original Message-
> From: Bastien [mailto:phps...@gmail.com]
> Sent: Sunday, December 12, 2010 9:20 AM
> To: Nathan Rixham
> Cc: Lester Caine; php-general List
> Subject: Re: [PHP] ORM doctrine
>
>
>
> On 2010-12-12, at 11:45 AM, Nathan Rixham wr
> -Original Message-
> From: Nathan Rixham [mailto:nrix...@gmail.com]
> Sent: Sunday, December 12, 2010 8:23 AM
> To: Tommy Pham
> Cc: 'Peter Lind'; php-general@lists.php.net; 'Lester Caine'
> Subject: Re: [PHP] ORM doctrine
>
> Tommy Pham wrot
Lester Caine wrote:
For fixed pages this is the best way of handling the information. And
handling those fixed pages is ... from my point of view ... not a
problem since they can be cached at that level, or even stored locally
in the browser cache. I've just been hitting re-load every time for
On Wed, Dec 8, 2010 at 10:02 PM, Tommy Pham wrote:
> Hi,
>
> Has anyone used doctrine before? I know Nathan mentioned it in the other
> thread but I was wondering how does it handle multi table joins query,
> about
> its performance and whether it uses any type of caching.
>
> Thanks,
> Tommy
Nathan Rixham wrote:
Lester Caine wrote:
Nathan Rixham wrote:
In your application itself, caching can be introduced at every level,
you've already got filesystem io caches provided by the operating
system, a well tuned db server cache can make a big difference as well,
then on to opcode caches
On 2010-12-12, at 11:45 AM, Nathan Rixham wrote:
> Lester Caine wrote:
>> Nathan Rixham wrote:
>>> In your application itself, caching can be introduced at every level,
>>> you've already got filesystem io caches provided by the operating
>>> system, a well tuned db server cache can make a big
Lester Caine wrote:
Nathan Rixham wrote:
In your application itself, caching can be introduced at every level,
you've already got filesystem io caches provided by the operating
system, a well tuned db server cache can make a big difference as well,
then on to opcode caches in languages like PHP
Nathan Rixham wrote:
In your application itself, caching can be introduced at every level,
you've already got filesystem io caches provided by the operating
system, a well tuned db server cache can make a big difference as well,
then on to opcode caches in languages like PHP since it's interprete
Tommy Pham wrote:
-Original Message-
From: Peter Lind [mailto:peter.e.l...@gmail.com]
Sent: Sunday, December 12, 2010 5:27 AM
To: Lester Caine
Cc: php-general@lists.php.net
Subject: Re: [PHP] ORM doctrine
The reason for 'caching' needs to be understood before it is
> -Original Message-
> From: Peter Lind [mailto:peter.e.l...@gmail.com]
> Sent: Sunday, December 12, 2010 5:27 AM
> To: Lester Caine
> Cc: php-general@lists.php.net
> Subject: Re: [PHP] ORM doctrine
>
> >
> > The reason for 'caching' nee
Hi All,
Apologies for wading in to this discussion, however I must point out
that caching at every level is very very important.
As Peter says, caching is not an optimization to be thought of later, it
is not the icing on the cake, rather, caching is one of the most
critical design factors,
On Sunday, 12 December 2010, Lester Caine wrote:
> Peter Lind wrote:
>
> I may have misunderstood the topic, but a cache to me is more than
> just storing views. It's also the db cache, memcache, apc, etc. You
> have to think about how you use these - some of them can't just be
> slapped on to you
On Sunday, 12 December 2010, Tommy Pham wrote:
>> -Original Message-
>> From: Lester Caine [mailto:les...@lsces.co.uk]
>> Sent: Sunday, December 12, 2010 2:10 AM
>> To: php-general List
>> Subject: Re: [PHP] ORM doctrine
>>
>> Peter Lind wrote:
&g
Peter Lind wrote:
I may have misunderstood the topic, but a cache to me is more than
just storing views. It's also the db cache, memcache, apc, etc. You
have to think about how you use these - some of them can't just be
slapped on to your app after development.
>> Data caching SHOULD always be
> -Original Message-
> From: Peter Lind [mailto:peter.e.l...@gmail.com]
> Sent: Sunday, December 12, 2010 3:05 AM
> To: Tommy Pham
> Cc: Lester Caine; php-general List
> Subject: Re: [PHP] ORM doctrine
>
> On Sunday, 12 December 2010, Tommy Pham
> wrote:
On Sunday, 12 December 2010, Tommy Pham wrote:
>> -Original Message-
>> From: Lester Caine [mailto:les...@lsces.co.uk]
>> Sent: Sunday, December 12, 2010 2:10 AM
>> To: php-general List
>> Subject: Re: [PHP] ORM doctrine
>>
>> Peter Lind wrote:
&g
> -Original Message-
> From: Lester Caine [mailto:les...@lsces.co.uk]
> Sent: Sunday, December 12, 2010 2:10 AM
> To: php-general List
> Subject: Re: [PHP] ORM doctrine
>
> Peter Lind wrote:
> > Your posts seem to indicate that caches are only useful when othe
> -Original Message-
> From: Peter Lind [mailto:peter.e.l...@gmail.com]
> Sent: Sunday, December 12, 2010 1:44 AM
> To: Tommy Pham
> Cc: php-general List
> Subject: Re: [PHP] ORM doctrine
>
> On Sunday, 12 December 2010, Tommy Pham
> wrote:
> >>
Peter Lind wrote:
Your posts seem to indicate that caches are only useful when other
parts of the app have been done wrong. My point was that this is a
fairly fundamental misunderstanding of caches - regardless of what you
are or aren't capable of optimizing.
CHACHES are only useful when there
On Sunday, 12 December 2010, Tommy Pham wrote:
>> -Original Message-
>> From: Peter Lind [mailto:peter.e.l...@gmail.com]
>> Sent: Sunday, December 12, 2010 1:18 AM
>> To: Tommy Pham
>> Cc: php-general List
>> Subject: Re: [PHP] ORM doctrine
>&
> -Original Message-
> From: Peter Lind [mailto:peter.e.l...@gmail.com]
> Sent: Sunday, December 12, 2010 1:18 AM
> To: Tommy Pham
> Cc: php-general List
> Subject: Re: [PHP] ORM doctrine
>
> > I understand cache well, both the benefits (save DB trip) and
>
> I understand cache well, both the benefits (save DB trip) and shortfalls
> (outdated by DB, management, etc.). Most of the apps that I've seen so far
> used cache to solve a problem that shouldn't happen in the 1st place. For
> example, during recent my quest looking PHP MVC framework and sa
> -Original Message-
> From: Peter Lind [mailto:peter.e.l...@gmail.com]
> Sent: Saturday, December 11, 2010 6:24 AM
> To: Tommy Pham
> Cc: php-general List
> Subject: Re: [PHP] ORM doctrine
>
> On Friday, 10 December 2010, Tommy Pham
> wrote:
>
> * snup
On Friday, 10 December 2010, Tommy Pham wrote:
* snup *
> The way I see it is this:
>
> 1) Thorough understanding of the problem: needs of the client/company,
> programming language in use, etc.
> 2) Thorough understanding of the objective of the application: answer the
> needs, capable of possi
On Thu, Dec 9, 2010 at 7:41 PM, Daevid Vincent wrote:
> I disagree. If you use a framework, then you're stuck with it. Bugs and all
>
(and trust me there are bugs and limitations you WILL run into).
I have fixed bugs locally in third party libraries; I have submitted them
for patching; I have r
On 10-12-10 11:38 AM, la...@garfieldtech.com wrote:
On 12/10/10 8:53 AM, Robert Cummings wrote:
Use PHP the way God intended it to be used.
Could you cite a reference for where God states his intentions on PHP?
Thanks,
Rob.
According to Rasmus, it's as a thin integration layer on top of
On 12/10/10 8:53 AM, Robert Cummings wrote:
Use PHP the way God intended it to be used.
Could you cite a reference for where God states his intentions on PHP?
Thanks,
Rob.
According to Rasmus, it's as a thin integration layer on top of PECL
modules written in C, most of which are just wrap
On Dec 10, 2010, at 11:20 AM, tedd wrote:
> At 9:53 AM -0500 12/10/10, Robert Cummings wrote:
>> On 10-12-09 10:41 PM, Daevid Vincent wrote:
>>>
>>> Use PHP the way God intended it to be used.
>>
>> Could you cite a reference for where God states his intentions on PHP?
>>
>> Thanks,
>> Rob.
>
> -Original Message-
> From: tedd [mailto:tedd.sperl...@gmail.com]
> Sent: Friday, December 10, 2010 8:20 AM
> To: Robert Cummings; Daevid Vincent
> Cc: php-general@lists.php.net
> Subject: Re: [PHP] ORM doctrine
>
> At 9:53 AM -0500 12/10/10, Robert Cummings wro
At 9:53 AM -0500 12/10/10, Robert Cummings wrote:
On 10-12-09 10:41 PM, Daevid Vincent wrote:
Use PHP the way God intended it to be used.
Could you cite a reference for where God states his intentions on PHP?
Thanks,
Rob.
Mark:7:34
And looking up to heaven, he sighed, and saith unto him,
Robert Cummings wrote:
Use PHP the way God intended it to be used.
Could you cite a reference for where God states his intentions on PHP?
Any PHP developers BLOG ;)
We are all gods ...
--
Lester Caine - G8HFL
-
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.C
On 10-12-09 10:41 PM, Daevid Vincent wrote:
-Original Message-
If you value CPU time over developer time, by all means avoid ORM
frameworks (and *all* frameworks). The point of a common
framework is to
trade a small bit of performance for a large amount of
developer time. If
you will
> -Original Message-
> From: Philip Thompson [mailto:philthath...@gmail.com]
> Sent: Thursday, December 09, 2010 10:59 PM
> To: php-general List
> Subject: Re: [PHP] ORM doctrine
>
> On Dec 10, 2010, at 12:00 AM, Paul M Foster wrote:
>
> > On Thu, Dec 09, 20
On Dec 10, 2010, at 12:00 AM, Paul M Foster wrote:
> On Thu, Dec 09, 2010 at 07:41:32PM -0800, Daevid Vincent wrote:
>>
>>> -Original Message-
If you value CPU time over developer time, by all means avoid ORM
frameworks (and *all* frameworks). The point of a common
>>> framework
On Thu, Dec 09, 2010 at 07:41:32PM -0800, Daevid Vincent wrote:
>
>
> > -Original Message-
> > > If you value CPU time over developer time, by all means avoid ORM
> > > frameworks (and *all* frameworks). The point of a common
> > framework is to
> > > trade a small bit of performance for
> -Original Message-
> From: Larry Garfield [mailto:la...@garfieldtech.com]
> Sent: Thursday, December 09, 2010 5:35 PM
> To: php-general@lists.php.net
> Subject: Re: [PHP] ORM doctrine
>
> On Thursday, December 09, 2010 12:45:38 pm David Harkness wrote:
> > O
> -Original Message-
> > If you value CPU time over developer time, by all means avoid ORM
> > frameworks (and *all* frameworks). The point of a common
> framework is to
> > trade a small bit of performance for a large amount of
> developer time. If
> > you will only use the framework
On Thursday, December 09, 2010 12:45:38 pm David Harkness wrote:
> On Wed, Dec 8, 2010 at 11:11 PM, Daevid Vincent wrote:
> > Avoid these ORM things like the plague! . . . Not to
> > mention all that fancy "ORM" doesn't come without a price. It costs in
> > terms
> > of speed, as well as training.
On Wed, Dec 8, 2010 at 11:11 PM, Daevid Vincent wrote:
> Avoid these ORM things like the plague! . . . Not to
> mention all that fancy "ORM" doesn't come without a price. It costs in
> terms
> of speed, as well as training.
>
If you value CPU time over developer time, by all means avoid ORM fram
On 10-12-09 02:11 AM, Daevid Vincent wrote:
Avoid these ORM things like the plague! They seem great in theory, but if
you're doing anything serious, they will quickly get in your way. Not to
mention all that fancy "ORM" doesn't come without a price. It costs in terms
of speed, as well as training
r off to make your custom
tools for your particular application.
-Original Message-
From: Alexandru Patranescu [mailto:dreal...@gmail.com]
Sent: Wednesday, December 08, 2010 9:10 PM
To: Tommy Pham
Cc: PHP
Subject: Re: [PHP] ORM doctrine
Doctrine is mature and well I've seen it plen
Doctrine is mature and well I've seen it plenty of times companies using
it.
Of course it handles multi table joins but I think it's main purpose is not
related to users writing joins... It's an ORM, you just read and write
objects.
Caching is something that must be there and you can read more on
46 matches
Mail list logo
