Re: Help, my developers are killing me with varchar2(4000)
Date: Mon, 11 Aug 2008 13:21:42 +0000 (UTC)
RogBaker_at_gmail.com wrote in news:fca4ed5e-1e56-4703-82fc-91ae3a35b1d1 @d1g2000hsg.googlegroups.com:
> I have a developer that created some tables in a development instnace
> and wants me to promote them to QA. I took a look at them, and nearly
> every column is varchar2(4000). I am pretty sure this is overkill for
> most of them. I know it takes up as much room as the data, but I just
> don't like this design philosophy. Does anyone have any references/
> urls saying this is a bad idea to design tables like this? It has been
> my experience that you get bad data by allowing columns to contain
> more data then what it should really hold.
Of course it is bad style, but the question why this actualls IS bad (i. e. what bad things will happen with it) still hasn't been answered in this discussion. Neither has the question been asked why Oracle doesn't support a random length string datatype.
W. Rösler Received on Mon Aug 11 2008 - 08:21:42 CDT