[BUGS] drop enum problem

2011-09-22 Thread Gavin Flower 

On a LInux 64 biut system:

$ psql
psql (9.1.0)
Type "help" for help.

gavin=> DROP TYPE raindow;
ERROR:  type "raindow" does not exist
gavin=> CREATE TYPE rainbow AS ENUM ('red', 'orange', 'yellow', 'green', 
'blue', 'purple');

ERROR:  type "rainbow" already exists
gavin=>


--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] drop enum problem

2011-09-22 Thread John R Pierce 

On 09/22/11 3:43 PM, Gavin Flower wrote:

gavin=> DROP TYPE raindow;
ERROR:  type "raindow" does not exist
gavin=> CREATE TYPE rainbow AS ENUM ('red', 'orange', 'yellow', 
'green', 'blue', 'purple');
ERROR:  type "rainbow" already exists 


PEBCAK.

drop type rainDow
create type rainBow 



--
john r pierceN 37, W 122
santa cruz ca mid-left coast


--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #6216: Calling PQconnectdbParams from C++ with a char**

2011-09-22 Thread Craig Ringer 

On 21/09/2011 4:25 PM, Lionel Elie Mamane wrote:

I added my initial patch, and as far as I understand, I have to send
the revised patch to the list before I can register it at the
commitfest. So here is my revised patch, that uses "const char *const * "
like elsewhere in the same file instead of "char const* const*".


Yep, I'm happy with that. It does what it says and no more.

I have *NOT* done any detailed testing, as I'm in the middle of moving 
house, but I find it hard to see how it can break anything that isn't 
its self incorrect. You can still pass a `char *' to a `const char * 
const' param, so it won't break any call sites.


--
Craig Ringer

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs