Re: Help, my developers are killing me with varchar2(4000)
Date: Mon, 28 Jul 2008 14:16:10 -0700 (PDT)
Message-ID: <0fd1522d-8de0-4680-98ad-c84248c4c0c8@k36g2000pri.googlegroups.com>
On Jul 28, 5:28 am, RogBa..._at_gmail.com wrote:
> 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,
I added it to the asktom post, but for completeness here: http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14261/datatypes.htm#sthref734
The part about having to make client arrays larger is probably more important that this, though.
jg
-- @home.com is bogus. "Besides, I do derive some professional amusement from breaking systems :-)" http://catless.ncl.ac.uk/Risks/25.24.html#subj5Received on Mon Jul 28 2008 - 16:16:10 CDT