Message-Id: <9111130243.AA27103@postgres.Berkeley.EDU>
From: smartin%lsican@mcnc.org (Stephen Martin)
Subject: Problems with PQtrace() and NULL
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
To: postgres@postgres.berkeley.edu
Date: Tue, 12 Nov 91 14:56:21 EST

I've noticed a couple of problems with postgres 3.0.

First if yoy use the PQtrace() feature from libpq, you must make sure to
set the external variable debug_port to the file pointer that you wish the
output to be printed on. Otherwise your program will core dump in the fprintf
statement in the debug routine. This doesn't seem to be documented anywhere.

Secondly, I'm having trouble replaceing a tuple that was created with a NULL
value for a char16 field. I've tried the following command:

replace address (street="leewood") where address.name="smith" and 
address.street=NULL\g

this causes the backend to exit. Should i be casting something here? Is there
something that would work with both null strings and zero length strings
(i.e. "")?
-- 
Stephen Martin               -------    LSI Logic Corporation of Canada, Inc.
Phone: (416) 620-7400     LSI|LOGIC|    Suite 1110, 401 The West Mall,        
Fax:   (416) 620-5005        |     |    Etobicoke, Ontario, Canada.
Email: smartin@lsican.uucp   -------    M9C 5J5
 or    smartin@Canada.lsil.com