On Thu, Sep 2, 2010 at 12:30 PM, Guillaume Lelarge <[email protected]> wrote: > Le 02/09/2010 10:28, Dave Page a écrit : >> Anyway, can the code in the edit grid be modified to detect the empty >> pgSet in place of null? >> > > Yeah, by checking how many rows were inserted. See patch attached. It > fixes the issue. Not sure this is the way we should do it. I'm afraid > there are other parts in the code where the "return new pgSet();" code > will bite us.
Looks OK to me. I don't expect many other places will have issues - we probably would have noticed by now. Besides, fixing occurrences like this is probably much easier than making reconnect work after an object has unexpectedly been handled a null pgSet. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise Postgres Company -- Sent via pgadmin-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers
