Skip site navigation (1) Skip section navigation (2)

Re: ILIKE

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: mlw <pgsql(at)mohawksoft(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>,PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ILIKE
Date: 2003-03-06 16:06:57
Message-ID: 200303061606.h26G6vf29159@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
I can comment on this --- adding a feature isn't zero cost.  There is
maintenance, but the larger cost is of users wading through features to
figure out if they need it or not.  We don't want to bloat ourselves to
the point PostgreSQL becomes harder to use.

Let's face it, you have to understand a feature before you can decide if
it useful to you.  Adding a feature that is of limited usefulness pushes
that analysis on every PostgreSQL users studying the PostgreSQL feature
set.

---------------------------------------------------------------------------

mlw wrote:
> I don't understand why you would want to remove a working feature. Even 
> if they are features which you do not like, why remove them? One of the 
> things about the PostgreSQL core team that troubles me is a fairly 
> arbitrary feature selection process.
> 
> It seems a feature has to be "liked" by someone for inclusion. I am 
> often taken by surprise by how you guys judge what the PostgreSQL 
> usership wants or "needs" based on your own perspective, and if someone 
> uses it differently, the reaction is fierce resistance.
> 
> The issue seems to be that there is some sort of feature phobia. Why 
> remove "ILIKE?" Why not just document an alternative for higher 
> performance?  Why can't you guys allow features even though you don't 
> necessarily agree? Yes, absolutely, assure the quality and accuracy of 
> the feature, but just ease up on the resistance. Allow things even 
> though you don't see the usefulness. Keep features even though you don't 
> agree with them.
> 
> One of the benefits of open source is the inclusiveness of contribution. 
> The plurality of development. The ability to harness the experience and 
> work of people around the world.  People with different objectives and 
> perspectives than yours.
> 
> In Open Source, the attitude should not be "do we want this feature?" 
> but "can we add/keep this without affecting anything else?" The first 
> argument is based on the assumption you know what everyone wants or 
> needs, which is preposterous, the second argument is based on how well 
> you know the PostgreSQL code and structure, which is a far more 
> reasonable position.
> 
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to

pgsql-hackers by date

Next:From: Merlin MoncureDate: 2003-03-06 16:26:46
Subject: Re: Win32 Powerfail testing
Previous:From: Justin CliftDate: 2003-03-06 16:03:56
Subject: Re: Who puts the Windows binaries on the FTP server?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group