Bill you have stepped out of line. You are flaming a person you obviously know nothing about, please be so kind to look at <a href="http://drupal.org/user/9446">http://drupal.org/user/9446</a><br><br><br><div><span class="gmail_quote">
On 1/16/08, <b class="gmail_sendername">Bill Moran</b> <<a href="mailto:wmoran@potentialtech.com">wmoran@potentialtech.com</a>> wrote:</span><blockquote class="gmail_quote" style="margin-top: 0; margin-right: 0; margin-bottom: 0; margin-left: 0; margin-left: 0.80ex; border-left-color: #cccccc; border-left-width: 1px; border-left-style: solid; padding-left: 1ex">
"Khalid Baheyeldin" <<a href="mailto:kb@2bits.com">kb@2bits.com</a>> wrote:<br>><br>> I have to applaud those who go out of their way to test on PostgreSQL.<br>> This is noble of you.<br>><br>> I may start doing it at some point even ... (I did some benchmarks with
<br>> a guy from the list helping, sorry forgot his name).<br><br>I believe that was me. I'm sorry I haven't had more time to help out,<br>but the personal issues I thought would be resolved by now are still<br>
a work in progress.<br><br>> But think of it: how scalable and sustainable is this? What about other<br>> databases? Will you do that for MS SQL (while running Mac/Linux?)<br>> Oracle?<br><br>The problem with this community is that it's oddly divided. Is Drupal
<br>going to be database agnostic or not? If the opinion of the community<br>is that supporting multiple databases is worthwhile, then folks need to<br>bite the bullet, accept that doing so is a _lot_ of work, and quit<br>
whining.<br><br>The fellow who starts these threads every month or so needs to quit his<br>damn whining and help out. His bitching is a constant distraction. And<br>his excuse that he doesn't care about PostgreSQL is bull. If Karoly
<br>doesn't care about a particular Drupal module, should everyone else quit<br>caring as well? If he doesn't want to support a less popular browser,<br>like Firefox, should Drupal quit caring?<br><br>Being database agnostic is not an easy goal. The weak of resolve need
<br>not apply as they'll fail anyway. But it seems to me that most of the<br>Drupal developers are not going to be easily dissuaded.<br><br>And why should they be? If Karoly convinced them to give up Postgres<br>support, next he'd convince them to give up IE support, then he'd scare
<br>them away from some other challenge or another. Great projects don't get<br>great by whining that "it's too hard" and backing down.<br><br>As many have pointed out, it's not really about PostgreSQL ... it's about
<br>supporting multiple databases. If Drupal drops PostgreSQL support, the<br>overall goal of supporting multiple databases will suffer. The approaches<br>that folks are taking to abstract the database are the correct approaches,
<br>but they're not as easy as just giving up, and they'll take time.<br><br>--<br>Bill Moran<br><a href="http://www.potentialtech.com">http://www.potentialtech.com</a><br></blockquote></div><br><br clear="all"><br>
-- <br>Oleg Terenchuk <br>Web Manager / Developer<br>Phone: 917 - 306 - 5653