Thread: Max Columns in a SQL Select

Max Columns in a SQL Select

From
PS PS
Date:
SQL Guru's,

Does anyone know what is the Column Limit in a SQL
Query in Oracle RDB version 7.1?  

I've about 200 columns in my SQL query.  Each column
is a computed column -- Case when a = b Then c Else 0
End.

It gives me a runtime error -- abnormal program
termination -- upon execution.  

Thanks a lot in advance.

    
__________________________________
Do you Yahoo!?
SBC Yahoo! - Internet access at a great low price.
http://promo.yahoo.com/sbc/


Re: Max Columns in a SQL Select

From
Richard Huxton
Date:
PS PS wrote:
> SQL Guru's,
> 
> Does anyone know what is the Column Limit in a SQL
> Query in Oracle RDB version 7.1?  
> 
> I've about 200 columns in my SQL query.  Each column
> is a computed column -- Case when a = b Then c Else 0
> End.

You'll probably want an Oracle mailing list - this is for PostgreSQL.


--   Richard Huxton  Archonet Ltd


Re: I'M Sorry!

From
Ricardo Maia
Date:
And sorry because the subject...

lol.

> On Tue, 2004-05-18 at 15:26, Ricardo Maia wrote:
> > Hi,
> > 
> > I'm from Brazil, and i have a question.
> > 
> > Exists some problem if i not uses the option "without oids"?
> > I read the manual, but I don't understand what I earn if i use it.
> > 
> > 
> > Thanks,
> > 
> > Ricardo.



Using "Without OIDs"

From
Richard Huxton
Date:
Ricardo Maia wrote:
> Hi,
> 
> I'm from Brazil, and i have a question.

Hi Ricardo, happy to help, but three points: 1. Always make sure you use "reply to all" on the PostgreSQL lists 2. For
anew question, send a new message to pgsql-sql@postgresql.org, 
 
since most direct email to this address goes into my spam bin. 3. You caught the subject-line change yourself in your
nextposting.
 

> Exists some problem if i not uses the option "without oids"?
> I read the manual, but I don't understand what I earn if i use it.

The OIDs are used by PostgreSQL's system tables. So, you can do 
something like  SELECT oid,relname,reltype FROM pg_class;
This will give you the number PG uses to refer to tables (etc.), the 
name you use and the type of thing it is. This type is also an OID.

These OIDs were never really meant to be for user-tables, but some 
people used them as a default primary-key. This was a bad idea, but 
since the column was always there you couldn't stop them.

The developers couldn't just turn OIDs off for user tables without 
breaking some applications, so they added an option to say you didn't 
want them. If you specify you don't want OIDs that table will use 4 
bytes less for every row, and so be a bit faster.

I believe in the next version, the default setting will be not to have 
OIDs and you will have to specify "WITH OIDS" if you do want them.

HTH
--   Richard Huxton  Archonet Ltd