From: | "Robins Tharakan" <tharakan(at)gmail(dot)com> |
---|---|
To: | "Dave Page" <dpage(at)pgadmin(dot)org> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: Obsolete "FORCE" option for REINDEX |
Date: | 2008-02-22 02:56:33 |
Message-ID: | 36af4bed0802211856hdec6fd8t36496f7a496b4d61@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hi Dave,
I too thought this was going to be simple :( Although this is not the final
patch, I am mailing this since its getting beyond intriguing to the zone of
becoming frustrating. This patch (attached) should have got the job done
yesterday itself... but the FORCE checkbox just doesn't go !!
Is there any other file (apart from frmMaintenance.xrc) where its position
could be set ? I cant understand how does a clean checkout (with this patch
applied) still get a force checkbox, after compilation ?
Any obvious dinosaurs that I am missing here ?
*Robins*
---------- Forwarded message ----------
From: Robins Tharakan <robins(at)pobox(dot)com>
Date: Thu, Feb 21, 2008 at 9:23 AM
Subject: Re: [pgadmin-hackers] Obsolete "FORCE" option for REINDEX
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: Erwin Brandstetter <brandstetter(at)falter(dot)at>,
pgadmin-hackers(at)postgresql(dot)org
*
*
>
>
> Thats a candidate for removal in the next release (anyone wanna pickup
> that little task?), but 1.8.x is advertised as supporting 7.3...
>
I'll give it a try.
*Robins*
Attachment | Content-Type | Size |
---|---|---|
remove_force_field.patch | text/x-patch | 2.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2008-02-22 07:32:48 | Re: Obsolete "FORCE" option for REINDEX |
Previous Message | Robins Tharakan | 2008-02-21 03:53:49 | Re: Obsolete "FORCE" option for REINDEX |