Hi, I am sure u probably know this already a leading null value column will take up a byte and like in the second case where the first column is null and the second column has a value the av row length is increased by 1 as the null takes up a byte. If the first col had a value and the second column had a null, then only the first one would have been stored. So its a good practice to put the columns with frequnet nulls at the end of the table so that it will decrease the ave row length and increase the data density.
Regards, Madhavan > But in a blockdump I just did, for a null row (tow columns both null) > there > is nothing in the dump, for second row(first col null, second has > value) the > first column value is shown as '*NULL*' I believe the discussion was > something related to how null and empty string is handled. But here > again in > 816 the empty strings are not shown once again. > > Oracle 8161 > -- Madhavan Amruthur DecisionPoint Applications -- http://fastmail.fm - You've just been FastMailed! -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Madhavan Amruthur INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
