Help, my developers are killing me with varchar2(4000)

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. Thanks in advance, Received on Mon Jul 28 2008 - 07:28:59 CDT