On Tue, Sep 1, 2009 at 10:55 AM, tedd wrote:
>
> I fully understand WHERE, it's understanding how JOIN's simplify things.
1. Joins make your sql more readable (and are a substatement to the
FROM clause, and should be indented)
2. When you use the WHERE clause, it is easy to accidentally do a
car
tedd wrote:
At 9:41 AM -0400 9/1/09, Andy Dirnberger wrote:
On Tue, Sep 1, 2009 at 8:58 AM, tedd wrote:
I need to understand joins much better than I do now because the
first query I fully understand while the second I don't.
Think of the WHERE clause as the filter. Use it to place res
At 9:41 AM -0400 9/1/09, Andy Dirnberger wrote:
On Tue, Sep 1, 2009 at 8:58 AM, tedd wrote:
I need to understand joins much better than I do now because the
first query I fully understand while the second I don't.
Think of the WHERE clause as the filter. Use it to place restrictions
on
tedd wrote:
> I need to understand joins much better than I do now
Same here. It's extremely helpful to see all these comparisons.
Bev
___
New York PHP User Group Community Talk Mailing List
http://lists.nyphp.org/mailman/listinfo/talk
http://www.nyph
> Essentially the thinking is that whenever you're processing code that
> involves a lot of tables or a lot of queries (and returned results),
> you end up with a bucketload of things named 'id' to handle.
>
> For instance imagine pulling out the contents of ten tables through ten
> queries i
On Tue, Sep 1, 2009 at 8:58 AM, tedd wrote:
>
> I need to understand joins much better than I do now because the first query
> I fully understand while the second I don't.
>
Think of the WHERE clause as the filter. Use it to place restrictions
on what information is returned.
WHERE price > 50
On Mon, Aug 31, 2009 at 8:22 AM, Kristina D. H.
Anderson wrote:
> I'm wondering why both phpMyAdmin and a number of the boilerplate PHP5
> frameworks' database code bases that I've seen all seem to be pushing
> the use of these delimiters around really, every single table and field
> name at all ti
At 8:13 AM -0400 9/1/09, Dan Cech wrote:
Michael Southwell wrote:
It's always seemed easier and clearer to me to use WHERE instead of JOIN
(where the table IDs are indeed named id, and the foreign keys are
labeled with the table name):
SELECT product_name, vendor_name
FROM product, vendor
Michael Southwell wrote:
> It's always seemed easier and clearer to me to use WHERE instead of JOIN
> (where the table IDs are indeed named id, and the foreign keys are
> labeled with the table name):
>
> SELECT product_name, vendor_name
> FROM product, vendor
> WHERE vendor.id = product.vendor_id
