RE: Odd virtual column error
- From: Michael.Coll-Barth@xxxxxxxxxxxxxxxxxxx
- To: "Oracle-L" <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 18 Aug 2008 10:40:38 -0400
> -----Original Message-----
> From: oracle-l-bounce@xxxxxxxxxxxxx
> [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of William Robertson
> Sent: Monday, August 18, 2008 10:32 AM
> To: Oracle-L
> Subject: Re: Odd virtual column error
>
> Agreed - why would you need a CHAR(4) for a 1-character
> substring of a 2-character column? Or for anything else, for
> that matter? CHAR is provided to look good in ANSI
> compatibility checklists, you are not supposed to actually use it.
>
>
> 2008/8/18 Stefan Knecht <knecht.stefan@xxxxxxxxx>
>
>
> Try using VARCHAR2(4) instead of CHAR(4) ?
>
> Cheers
>
> Stefan
::Applause:: Now to convince those around me.
However, how do you feel about char(1) vs varchar2(1)? <--- size of one
byte.
And, what overhead, if any, is there in having a varchar2 column defined
as a much bigger field that you think you will ever need? Too many
times have I seen requests for varchar2(10) to varchar2(12) only to see
it expanded again at a later date. Why not make it varchar2(40)?
The information contained in this message and any attachment may be
proprietary, confidential, and privileged or subject to the work
product doctrine and thus protected from disclosure. If the reader
of this message is not the intended recipient, or an employee or
agent responsible for delivering this message to the intended
recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited.
If you have received this communication in error, please notify me
immediately by replying to this message and deleting it and all
copies and backups thereof. Thank you.
--
//www.freelists.org/webpage/oracle-l
Other related posts:
