Re: Lightspeed for frmQuery and other issues.
От | Andreas Pflug |
---|---|
Тема | Re: Lightspeed for frmQuery and other issues. |
Дата | |
Msg-id | 4454E464.7020207@pse-consulting.de обсуждение исходный текст |
Ответ на | Re: Lightspeed for frmQuery and other issues. ("Dave Page" <dpage@vale-housing.co.uk>) |
Список | pgadmin-hackers |
Dave Page wrote: > > -----Original Message----- > From: "Andreas Pflug"<pgadmin@pse-consulting.de> > Sent: 30/04/06 16:19:51 > To: "Dave Page"<dpage@vale-housing.co.uk> > Cc: "pgadmin-hackers@postgresql.org"<pgadmin-hackers@postgresql.org> > Subject: Re: Lightspeed for frmQuery and other issues. > >>It wasn't removed explicitely, but the underlying class that didn't meet >>the requirement was backed out. You've painted the wall before >>wallpapering it. > > > Quickreport sat over that class as well - is that now broken too? That's in frmQuery only, right? If so, the local solution is fine. If it's more global, it should go somehow to dlgClasses. > > Please restore the functionality or I will back out the patch until it is completed in it's entirety. Which functionality? > > You complain about the work that led to significant speed increase from the original code, but at least we busted a gutto make sure it didn't break any existing functionality. Again: I said early enough the base was wrong. And I didn't see *any* speed increase on linux. Probably, any virtual solution will be ok, but any non-virtual solution *cant* be ok. > > >>It's not a problem of the factories, they do what they should and will >>work *if used*. > > > Like I said, I'll look at this. I didn't grok that the failed attempt you mentioned was only a minor rejig. It should have been, but things are horribly intervowen. I'd have to understand in detail what's going on to continue, because apparently removing MNU_XXX entries would kill methods too. Regards, Andreas
В списке pgadmin-hackers по дате отправления: