> Not in my opinion. The interface has to return the value for the > column, not > te desired presentation of that value. > Besides it makes you unable to check for NULL columns.
That's true. But I might be willing to give that up in certain cases. > And how are you goint to insert a NULL value? What should the database do > when it receives undef, "" or "NULL" in an insert statement? > Why would you want this feature besides from being able to print it out > nicely? A good point. Perhaps the attribute could be something like "NULL_RETRIEVAL_VALUE" to apply only when retrieving null values. Printing out values in one way or another would probably be the only good use of this feature. But I think that is by itself a pretty good reason.
