----- Original Message ----- From: "Mitch Helle-Morrissey" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, January 04, 2002 6:18 PM Subject: RE: mapping NULL values
> > Your problem is not a database problem, but a presentation problem. > > So to keep things clean you should solve it when representing the data and > > not in the database interface. > > But isn't the problem of translating the database's notion of NULL to Perl > the interface's issue? 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. 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? > > So you could write two special print subs to print rows, or > > special subs to > > transform rowdata. > > That's exactly what I'm doing now. I know how to do it, it's just that I'd > rather not have to all the time. I think that is the way. Messing around with NULL values might give unpredicatble problems. Good luck, Maarten.
