Re: Should we consider empty fields as NULL values when dealing with string columns ?

From: "Rod K" <rod(at)23net(dot)net>
To: "Nagib Abi Fadel" <nagib(dot)abi-fadel(at)usj(dot)edu(dot)lb>, "generalpost" <pgsql-general(at)postgresql(dot)org>, "developPost" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Should we consider empty fields as NULL values when dealing with string columns ?
Date: 2003-12-11 16:00:29
Message-ID: KNEPILBLIADCDMMPIKIKAEIGDMAA.rod@23net.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

The rest of your post was answered, but I'll add the following. You should
set your error_reporting level higher, so you are warned if you are
referencing an unassigned variable. There is something wrong with your
script if you aren't validating data.
When using script languages (like PHP) if by mistake the variable is not
defined such insert is possible (let's say we have a variable $col1_value
and after a long day of work we make a mistake and write it $col_value).

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Craig Stratton 2003-12-11 16:01:19 pqReadData() -- read() failed: errno=32
Previous Message Tom Lane 2003-12-11 15:56:03 Re: ERROR: did not find '}' at end of input node (again)

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2003-12-11 16:23:02 Re: 7.4 build problem on Linux Vserver
Previous Message Tino Wildenhain 2003-12-11 15:48:28 Re: Should we consider empty fields as NULL values when