Re: Difference between "SELECT *" and "SELECT COLUMN1, ..., COLUMNN"

The LONG is the problem..
I think that ,because here is no way to determine the size of the LONG , any attempt to retrieve something AFTER the LONG will fail, because the parser won't know when the LONG ends and the next field begins..

"Brian Ross" <brian.ross_at_home.com> wrote:

>> > I am having a problem where if I execute a query using "SELECT
>> > *" I don't have any records returned even though I know there
>> > should be. If I change it to "SELECT COLUMN1, etc" the record
>> > is returned successfuly. There are no errors or warnings
>> > returned in the first case. What could be causing the first
>> > select to fail?
>>
>> Are you using some programming language for this and can't
>> retrieve from a cursor, or is this happening in SQLPlus?
>>
>> If former, can you check if the query runs correctly in SQLPlus
>> first?
>
>It is from a programming language (ADO/C++). The query runs OK when I run
>from an external query program.
>
>It seems that this has something to do with a column being the 'LONG'
>datatype and the order of the columns that are selected. If I move the name
>for the LONG column to the end of the SELECT list I can now retrieve my
>recordset. If there are any columns selected after the long column then my
>recordset won't have any records.
>
>I am beginning to think this may be more of an ADO/ODBC issue but it would
>be great if anyone has any suggestions as to what might be the proper
>solution?
>
>

-----= Posted via Newsfeeds.Com, Uncensored Usenet News =----- http://www.newsfeeds.com - The #1 Newsgroup Service in the World!  Check out our new Unlimited Server. No Download or Time Limits! -----== Over 80,000 Newsgroups - 19 Different Servers! ==----- Received on Wed Aug 29 2001 - 11:30:56 CDT