Re: [PHP] object persistence within a session




But joins are what relation databases excel at, so PHP would be the
bottleneck in your example.

Not always...

If your JOIN can not be easily constrained in the query, until some kind of processing of the result set takes place, you can end up with a monster interim result set that will swap the DB server, and send it to its knees.

For example, if you need a result set of 10 items, some of which (but not all) relate to a second table, and the left outer join the generates millions of rows...

Also:

SQL is great at many things.

But something like a tree traversal or other results that depend on the rows returned can be a real bear, especially for pages that are not your core scalable must-have part of the site -- Where you don't want to complicate everything else for just this one admin/report page.

I'm only saying that, on occasion, the dozen DB calls wins out over a JOIN that swaps madly.

.



Relevant Pages

  • Re: [PHP] object persistence within a session
    ... bottleneck in your example. ... If your JOIN can not be easily constrained in the query, until some kind of processing of the result set takes place, you can end up with a monster interim result set that will swap the DB server, and send it to its knees. ... I'm only saying that, on occasion, the dozen DB calls wins out over a JOIN that swaps madly. ...
    (php.general)
  • Re: Cluster synchronize
    ... queries per unit time. ... CPU is the ONLY bottleneck. ... increase in query capacity. ... queries that perform sequential I/O or queries performing random I/O. ...
    (microsoft.public.sqlserver.clustering)
  • RE: Using multiple 1 to 1 relationships
    ... record in TermInfo and then somehow working with OTHER tables in a view query ... In your second post you didn't describe / confirm your join types. ... You keep saying just "failure" without saying what the ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Parameters in queries
    ... I believe that is exactly what I am saying, ... the 2nd query should use todays date instead of the parameter. ... ie both queries should use the same subquery not 2 separate ... WHERE BBIdentifier Not In (SELECT BBIdentifier ...
    (microsoft.public.access.formscoding)
  • Re: One-To-One Relationships
    ... Of course it isn't easy to query; ... I'm just saying I may not yet have ... don't exist outside of their attributes, good (that was a painful one ... Understanding the impact that object containment has on ...
    (comp.databases.theory)