Re: [pgadmin-hackers] Need help with GTK bug
Hiroshi Saito wrote: Hi Dave. It is the countermeasure of the problem which is still contained. My FreeBSD improves only a little by this coping. However, Check it because it may have badness besides if it is applied. not a request for application but this is reference information. I trust only the result which did try in the reality. Seeing is believing.:-) regards, Hiroshi Saito This is an interesting approach. Usually, the this pointer should contain the same as event.GetEventObject(). If it doesn't there's something wrong, but it's wx's responsibility to provide a correct pointer. You might have breakpoints at the OnSize methods, and trace back where they come from. Regards, Andreas ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [pgadmin-hackers] Need help with GTK bug
Hi Andreas. From: "Andreas Pflug" <[EMAIL PROTECTED]> > This is an interesting approach. Usually, the this pointer should > contain the same as event.GetEventObject(). If it doesn't there's > something wrong, but it's wx's responsibility to provide a correct > pointer. You might have breakpoints at the OnSize methods, and trace > back where they come from. Yes,It is probably as you say if it is usual. This problem is very complex for me. I gets confused when this is read:-( It is a plan as a beginning of the solution at the time of the present. regards, Hiroshi Saito ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[pgadmin-hackers] The indication mistake of unique index(multi column)
Hi Dave. The second line isn't indicated in the property columns of unique index (multi column). Please Apply it. ex.) CREATE TABLE (a int, b int, unique(a,b)); b is missing, and falls. regards, Hiroshi Saito dlgIndex_patch Description: Binary data ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
