Re: blank fields in Oracle

Well, testing is always a good thing, isn't it? I'd strongly recommend the Db Management team to get acquainted with the product before imposing best practices to others. If all fields are declared as varchar2, then you will get null values or possibly run-time errors whenever you come across a zero length string like a trimmed one and you try to store it. Of course you might trap this in a trigger, but why bother if you can just work around it by using a CHAR? Simple is better, always.

Bye,
Flavio Received on Thu Mar 13 2003 - 11:20:50 CST