Comments on: SQL Join syntax: Theta vs ANSI http://www.jellyandcustard.com/2006/08/10/sql-join-syntax-theta-vs-ansi/ Web Development Blog Sat, 05 Jul 2008 00:12:22 +0000 http://wordpress.org/?v=2.0.2 by: Nested queries, SQL_CALC_FOUND_ROWS (MySQL) | The Montoya Herald http://www.jellyandcustard.com/2006/08/10/sql-join-syntax-theta-vs-ansi/#comment-18525 Thu, 18 Oct 2007 02:44:31 +0000 http://www.jellyandcustard.com/2006/08/10/sql-join-syntax-theta-vs-ansi/#comment-18525 [...] Looking at this now, this query could be further optimized. I’m doing a cross-join on sends and haikus to get all the haiku sent to the userID, but cross-joins are heavy. This nested query is a “Theta” style join, which is now discouraged in favor of the more standard “ANSI” style joins (the kinds that use JOIN … ON/USING). From Jelly and Custard: “Theta style joins in general (and in my experience) are notably resource intenstive (sic) compared to ANSI equivalents.” [...] […] Looking at this now, this query could be further optimized. I'm doing a cross-join on sends and haikus to get all the haiku sent to the userID, but cross-joins are heavy. This nested query is a "Theta" style join, which is now discouraged in favor of the more standard "ANSI" style joins (the kinds that use JOIN … ON/USING). From Jelly and Custard: "Theta style joins in general (and in my experience) are notably resource intenstive (sic) compared to ANSI equivalents." […]

]]> by: John Hirbour http://www.jellyandcustard.com/2006/08/10/sql-join-syntax-theta-vs-ansi/#comment-687 Thu, 17 Aug 2006 04:15:11 +0000 http://www.jellyandcustard.com/2006/08/10/sql-join-syntax-theta-vs-ansi/#comment-687 Finally an article explaining this.... a lot of Oracle DBAs have told me that the Theta syntax is the "right one". What BS!!! I'd agree that the ANSI snytax is easier to read.... easier to debug... and nicer looking! Plus it allows you to seperate what joins your table from your selection criteria. Finally an article explaining this…. a lot of Oracle DBAs have told me that the Theta syntax is the "right one". What BS!!! I'd agree that the ANSI snytax is easier to read…. easier to debug… and nicer looking!

Plus it allows you to seperate what joins your table from your selection criteria.

]]> by: Ross Notes » Blog Archive » links for 2006-08-16 http://www.jellyandcustard.com/2006/08/10/sql-join-syntax-theta-vs-ansi/#comment-683 Wed, 16 Aug 2006 12:25:19 +0000 http://www.jellyandcustard.com/2006/08/10/sql-join-syntax-theta-vs-ansi/#comment-683 [...] SQL Join syntax: Theta vs ANSI · Jelly and Custard (tags: sql) [...] […] SQL Join syntax: Theta vs ANSI · Jelly and Custard (tags: sql) […]

]]> by: FuzzyBlog » Blog Archive » Good article on SQL Joins http://www.jellyandcustard.com/2006/08/10/sql-join-syntax-theta-vs-ansi/#comment-680 Tue, 15 Aug 2006 10:45:25 +0000 http://www.jellyandcustard.com/2006/08/10/sql-join-syntax-theta-vs-ansi/#comment-680 [...] JellyAndCustard has a good article on SQL Joins: At the heart of every dynamic website is some form of data source, whether it’s a simple flat text file, XML schema, or full blown database. In this article, I’ll be addressing database table joins with SQL (specifically MySQL). Good database design should adhere to the third normal form, or “3NF”. In a nutshell, relating bits of data to other bits of data with minimal memory/storage overheads. In order to utilise a 3NF database effectively, table joins (linking and extracting data from two different internal sources) are an absolute must. In standard Structured Query Language syntax, there are two main join-types: theta and ANSI. More… [...] […] JellyAndCustard has a good article on SQL Joins: At the heart of every dynamic website is some form of data source, whether it's a simple flat text file, XML schema, or full blown database. In this article, I'll be addressing database table joins with SQL (specifically MySQL). Good database design should adhere to the third normal form, or "3NF". In a nutshell, relating bits of data to other bits of data with minimal memory/storage overheads. In order to utilise a 3NF database effectively, table joins (linking and extracting data from two different internal sources) are an absolute must. In standard Structured Query Language syntax, there are two main join-types: theta and ANSI. More… […]

]]>