Skip site navigation (1) Skip section navigation (2)

Re: Error calling PG_RETURN_NULL()

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alexandre Savaris <alexandre(dot)savaris(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Error calling PG_RETURN_NULL()
Date: 2011-07-26 03:25:18
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-hackers
Alexandre Savaris <alexandre(dot)savaris(at)gmail(dot)com> writes:
> Hi! I'm working on an implementation for a new data type (PostgreSQL 
> version 9.1 beta 3 on Windows 7 32 bits), according to the following rules:
> - 1. NULL values are stored as is;
> - 2. character strings (up to 16 bytes) are stored without leading or 
> trailing spaces;
> - 3. empty character strings are stored as NULL values.

*buzzz* wrong answer, thanks for playing.

Data types do not get to editorialize on null versus not null.  Forget
your cute idea #3, and you'll be much happier.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2011-07-26 04:19:08
Subject: Re: Check constraints on partition parents only?
Previous:From: Jeff DavisDate: 2011-07-26 03:15:45
Subject: Re: [HACKERS] Error calling PG_RETURN_NULL()

pgsql-general by date

Next:From: Toby CorkindaleDate: 2011-07-26 05:29:13
Subject: practical Fail-over methods (was: streaming replication trigger file)
Previous:From: Tom LaneDate: 2011-07-26 03:19:55
Subject: Re: pgsql error

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group