X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org
Received: from localhost (neptune.hub.org [200.46.204.2])
	by svr1.postgresql.org (Postfix) with ESMTP id 202ABD1DF84
	for <pgsql-general-postgresql.org@localhost.postgresql.org>;
	Thu, 11 Dec 2003 15:59:29 +0000 (GMT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024)
	with ESMTP id 59990-10
	for <pgsql-general-postgresql.org@localhost.postgresql.org>;
	Thu, 11 Dec 2003 11:58:58 -0400 (AST)
Received: from server.yourfacility.com (server.yourfacility.com
	[207.103.74.10])
	by svr1.postgresql.org (Postfix) with SMTP id 1DB4DD1DF93
	for <pgsql-general@postgresql.org>;
	Thu, 11 Dec 2003 11:58:53 -0400 (AST)
Received: (qmail 37558 invoked by uid 0); 11 Dec 2003 15:58:44 -0000
Received: from unknown (HELO ROD) (141.149.246.2)
	by server.yourfacility.com with SMTP; 11 Dec 2003 15:58:44 -0000
From: "Rod K" <rod@23net.net>
To: "Nagib Abi Fadel" <nagib.abi-fadel@usj.edu.lb>,
	"generalpost" <pgsql-general@postgresql.org>,
	"developPost" <pgsql-hackers@postgresql.org>
Subject: Re: Should we consider empty fields as NULL values when dealing with
	string columns ?
Date: Thu, 11 Dec 2003 11:00:29 -0500
Message-ID: <KNEPILBLIADCDMMPIKIKAEIGDMAA.rod@23net.net>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_065E_01C3BFD5.FD0C8020"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <001401c3bff4$49abd7f0$f664a8c0@nagib>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
X-Virus-Scanned: by amavisd-new at postgresql.org
X-Spam-Status: No, hits=1.0 tagged_above=0.0 required=5.0 tests=HTML_30_40,
	HTML_FONT_COLOR_BLUE, IN_REP_TO, MSGID_GOOD_EXCHANGE, RCVD_IN_NJABL
X-Spam-Level: *
X-Archive-Number: 200312/637
X-Sequence-Number: 54031

This is a multi-part message in MIME format.

------=_NextPart_000_065E_01C3BFD5.FD0C8020
Content-Type: text/plain;
	charset="windows-1256"
Content-Transfer-Encoding: 7bit

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).

------=_NextPart_000_065E_01C3BFD5.FD0C8020
Content-Type: text/html;
	charset="windows-1256"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dwindows-125=
6">
<META content=3D"MSHTML 6.00.2800.1276" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><SPAN class=3D457055715-11122003><FONT color=3D#0000ff size=3D2>The re=
st of your=20
post was answered, but I'll add the following.&nbsp; You should set your=20
error_reporting level higher, so you are warned if you are referencing an=
=20
unassigned variable.&nbsp; There is something wrong with your script if you=
=20
aren't validating data.</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV><FONT face=3DArial size=3D2>When using script languages (like PHP) i=
f by=20
  mistake the variable is not defined&nbsp;such insert is&nbsp;possible (le=
t's=20
  say&nbsp;we have a variable $col1_value and after a long day of work&nbsp=
;we=20
  make a mistake and write it $col_value).</FONT></DIV></BLOCKQUOTE></BODY>=
</HTML>

------=_NextPart_000_065E_01C3BFD5.FD0C8020--