Re: Prepping to break every past release...

In response to Dave Page <dpage(at)pgadmin(dot)org>:

> On Wed, Mar 4, 2009 at 9:09 PM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
>
> >> I assume you'll be putting in the weeks/months of work required to fix
> >> pgAdmin & phpPgAdmin which would be far better spent on new features
> >> than uglifying the code in far nastier ways than the current state of
> >> the catalogs?
> >
> > *Shrug* long term consistency is the better choice.
>
> Easy to say if you're not one of the people for whom such a change
> would mean weeks of recoding

Don't those folks have to tweak their code with each new release anyway?
Because those tables are constantly changing? I know we hit problems
with the way triggers are stored in 8.3 compared to earlier versions.

Granted, a sweeping change will necessitate a much larger tweak than
a few changed columns, but the long-term benefit should be cleaner
client code.

> Besides - what percentage of users ever go anywhere near the
> catalogs? I'd guess a fraction of a percent of users, and maybe 1 - 5%
> of developers.

You could always take a survey ... bosses love surveys ...

I, for one, know of lots of code that I've written that accesses those
catalogs. I can't speak for other people.

--
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/