Peter Hunsberger wrote:
>>> I still don't get it. I do want a zero for the subversion_flags to be
>>> stored in the table. But it returned an error because it didn't like
>>> subversion_flags='' in the UPDATE SQL statement.
>>> subversion_flags | integer | not null default 0
>> Right.
On Sun, Apr 04, 2010 at 08:03:13PM -0700, Wang, Mary Y wrote:
> I still don't get it. I do want a zero for the subversion_flags to be stored
> in the table. But it returned an error because it didn't like
> subversion_flags='' in the UPDATE SQL statement.
>
> subversion_flags | integer
On Sun, Apr 4, 2010 at 10:23 PM, Scott Marlowe wrote:
> On Sun, Apr 4, 2010 at 9:03 PM, Wang, Mary Y wrote:
>> I still don't get it. I do want a zero for the subversion_flags to be
>> stored in the table. But it returned an error because it didn't like
>> subversion_flags='' in the UPDATE SQL
On Sun, Apr 4, 2010 at 9:03 PM, Wang, Mary Y wrote:
> I still don't get it. I do want a zero for the subversion_flags to be stored
> in the table. But it returned an error because it didn't like
> subversion_flags='' in the UPDATE SQL statement.
>
> subversion_flags | integer | not null
-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Sunday, April 04, 2010 7:50 PM
To: Wang, Mary Y
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Null vs. Empty String in Postgres 8.3.8
"Wang, Mary Y" writes:
> Can someone provide a link to the Postgres 8.x documenta
"Wang, Mary Y" writes:
> Can someone provide a link to the Postgres 8.x documentation that provides
> information about Null vs. Empty String?
> Here is the situation:
> Currently, the source code performs the following SQL statement :
> UPDATE user_group set subversion_flags='' WHERE user_id='5
Can someone provide a link to the Postgres 8.x documentation that provides
information about Null vs. Empty String?
Here is the situation:
Currently, the source code performs the following SQL statement :
UPDATE user_group set subversion_flags='' WHERE user_id='5818' AND
group_id='438';
(This SQ