Re: Varchar2 vs Char

: > I've been getting feedback from the developers arguing that using varchar2
: > instead of char when defining a table is taking a performance hit. Does anyone

Where's the performance hit, when they are defining the table ? I'd live with that :)

Ask them what is taking a performance hit, get them to prove it to you, tell them to tune their code and SQL *and* then tell them that the coding standards only allow the use of VARCHAR2 !

IAP

--
In an attempt to reduce junk email I use an invalid 'From' address.
My correct email address can can be determined by replacing 'not.valid' with 
'value.net'