Re: [COMMITTERS] pgsql/src/interfaces/libpgeasy (libpgeasy.c) - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [COMMITTERS] pgsql/src/interfaces/libpgeasy (libpgeasy.c)
Date
Msg-id 199912200234.VAA20543@candle.pha.pa.us
Whole thread Raw
Responses Re: [HACKERS] Re: [COMMITTERS] pgsql/src/interfaces/libpgeasy (libpgeasy.c)
List pgsql-hackers
>   Date: Sunday, December 19, 1999 @ 20:31:26
> Author: tgl
> 
> Update of /usr/local/cvsroot/pgsql/src/interfaces/libpgeasy
>      from hub.org:/home/tmp/cvs-serv86291
> 
> Modified Files:
>     libpgeasy.c 
> 
> -----------------------------  Log Message  -----------------------------
> 
> Clean up some minor gcc warnings.  I'm not touching the
> major one, though, which is the truly ugly stores into libpq private
> storage.  Can't you find a better way to do this?

Yes, very ugly.  I need some way to store my state information _inside_
the Result structure.  Any ideas?

Or is this going to be another one of those, "Hey, who put the LIKE
indexing in gram.y...  Oh, it was you Momjian...  Well, no, I can't
think of a better way right now..."  Two years pass until someone
improves it.  :-)

--  Bruce Momjian                        |  http://www.op.net/~candle maillist@candle.pha.pa.us            |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pgindent (Re: [HACKERS] LONG varsize - how to go on)t
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock