Thanks, I've committed a fix to SVN for thes issues. Regards, Dave
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Erwin Brandstetter > Sent: 16 October 2006 04:21 > To: pgadmin-support@postgresql.org > Subject: Re: [pgadmin-support] Minor bug: Refreshing type in > object orowser fails > > Same (or similar) bug is present in the listing of indexes > (under table). > Also, unique constraints and primary keys - while listed under > constraints - erroneously show the SQL script of the first > _index_ after > a refresh. Probably because these kinds of constraints create > an index > and therefore share the index bug.. > > Again, the error is persistent until the whole branch is refreshed. > Also present in v1.4.2. > > Regards > Erwin Brandstetter > > > [EMAIL PROTECTED] wrote: > > Hi developers! > > > > I am testing pgAdmin III Beta 2 (Oct 3 2006, re: 5426:5427) > on Windows > > XP (latest patch level). > > > > When I set the focus on any type in the object browser and > hit F5 (or > > chose "refresh" from the menu) the SQL pane incorrectly > displays the > > definition of the _first_ type in the list, no matter which > type I had > > selected. Clicking somewhere else and on the type again does not > > remedy the error. Only refreshing the whole type section does. > > > > Only in the type-chapter, the others are doing fine. > > This bug is also present in v1.4.2. > > > > Regards > > Erwin Brandstetter > > > > ---------------------------(end of > broadcast)--------------------------- > TIP 4: Have you searched our list archives? > > http://archives.postgresql.org > ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
