> -----Original Message-----
> From: Andreas Pflug [mailto:[EMAIL PROTECTED]
> Sent: 20 June 2003 17:52
> To: [EMAIL PROTECTED]; Dave Page
> Subject: pgAdmin3 feature freeze?
>
>
> Exporting of data from the sql window is implemented now.
>
> I had a deep look at CREATE OPERATOR CLASS, and decided to to
> implement
> a property dialog these days. To program it in a way that's worth it,
> the dialog should be really intelligent about those strategy numbers.
> That's not a problem per se, but a lot of work for very few
> people using
> it. I believe missing this won't be a big drawback.
OK, sounds good.
While I think of it - one bug I noticed today but haven't been able too
look at:- I have a table with a serial pkey, specified not null. I
cannot add rows to it, because if I leave the column blank, the editor
tries to set it to null::int4.
> TODO.txt is updated accordingly.
>
> To give some hints about bug reporting, I added an entry to the help
> menu. It uses the file src/bugreport.html.
> For release, we could either remove that menu or replace it
> with a real
> form, that posts to the pgadmin website/mailing list.
OK.
So people - any more essential features? Shout now or forever hold your
peace (well, until the next release anyhoo)!!
Regards, Dave.
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
