[development] Do not let postgresql hold back great patches

Karoly Negyesi karoly at negyesi.net
Fri Nov 16 22:49:51 UTC 2007

> > In my opinion, any patch should be committable to core once it works
> > on mysql and has a decent hope (use common sense) to work on
> > postgresql. 

> No. Supporting multiple databases is a good thing and something we  
> want to get better at.

We agree.

> I'm not willing to drop PostgreSQL support

Same as I answered to Barry. Somebody care to explain how my words can mean "drop postgresql support" How? I said " a decent hope (use common sense) to work on postgresql." by (use common sense) I meant "please do not debate on what's a decent hope". All I asked for is to commit something, move on and let the postgresql people test/fix once it's in thus not letting the very limited postgresql testing community hold back the whole of Drupal.

In the past we committed patches that were incomplete one way or another so we could build on them. That's all I am asking here.

I am working on the LOWER patch. I have carefully worded the original letter I am following up to now. I am truly baffled that despite all these efforts, people think I want to drop PostgreSQL. If you can point that out in my letters or my work, I would be grateful because surely all these great people take that motion from somewhere but where...? Maybe my blog post? But some people did not like it, so I yielded to fate and try to find solutions that are good for everyone.

More information about the development mailing list