Re: Limit of 1050 columns for ANSI joins

Mladen Gogala wrote:
> On Wed, 07 Jun 2006 05:06:33 -0700, Andreas Sheriff wrote:
>
> > Yeah, yeah, so I have 1095 columns (For online surveys, those data points
> > really add up, and this is a small survey...), that doesn't mean I should be
> > limited, should I?
> > Can anyone find a reference in the Oracle documentation that states 1050 as
> > a column limit for ANSI joins? I see a 1000 column limit for tables, but it
> > doesn't say anything about views or ANSI joins.
>
> Then don't use ANSI joins. Oracle has the corresponding syntax, which is
> more logical and causes less problems with performance and optimization
> then ANSI joins. Personally, I find ANSI joins clumsy and plain stupid.
> ANSI joins provide the illusion that your SQL is, somehow, portable.
> Oracle probably supported ANSI joins just because everybody else did, but
> those monstrosities break the spirit of SQL. Tedd Codd probably died when
> he saw ANSI join syntax being called SQL. SQL is a language that was
> modeled after naive set theory, which means that it provides criteria for
> selecting various elements from the given set. Unfortunately, developers
> are somehow entranced by this idiotic construct and still prefer it over
> the nice logical Oracle syntax.
>
> --
> http://www.mgogala.com

I thought the Oracle limit of 1000 columns in a table also applied to a view:

>From 9.2 SQL manual >>

AS subquery
Specify a subquery that identifies columns and rows of the table(s) that the view is based on. The select list of the subquery can contain up to 1000 expressions.
<<

• Mark D Powell --