> >> In fact, I already emailed the developers yesterday, and asked if I > >> could > >> pay to have the particular feature I wanted prioritized at this time. > > > >Strange how open source developers don't always answer to the almighty > >dollar, eh? > > > > I asked kindly that you not turn this into a personal attack on me. Can I > please ask you to stop???? > > I am showing you respect by not responding on this point, other than to say > please don't go there. >
Maybe you misinterpreted what he said -- I didn't read that as a personal attack. I think he was commenting on the MySQL developers, not you. > >Adding subselects to MySQL is a feature that many, many people have > >requested; > > > How many? And how many users of MySQL are there? And how many of MySQL > could there potentially be? > Some of the most common newie questions on this list have to do with subselects -- "even Access has subselects" :) > > > I haven't searched the list archives, but I've > >been subscribed to this list for a long time, and I can't recall even > >one other person requesting that the DEFAULT behavior be modified. > > > That is my pet issue perhaps. Obviously one would not fork over one small > issue like that. You are dragging the other thread into this one. I am > thinking of a much wider issue, which is how can I be sure that my > investment in and use of MySQL will not be overcome by other forces which > desire that it be something very different. When I first authorized the > use of MySQL, I was told that is was focused on simplicity, speed, and > every improving SQL compliance (i.e. that the little thorns would not be > ignored forever). > Some of the biggest complaints about MySQL's SQL non-compliance have to do with subselects and referential integrity. > You may very well be correct, that it is alarmist to assume that the little > SQL mistakes won't be fixed fully soon. And that other little issues that > keep a product from being perfect at the fundamental level, won't be > ignored. You may be right about that. Then again, you may not be. But I > have investment to worry about. For others who have investment to worry > about, they may look at 4.0 and ask themselves what they are getting, and > whether they feel secure about the improvement that has been made since the > last major milestone. > > For me, I would have rather seen many issues towards further stability and > correctness, versus launching into other huge markets (embedded and > high-end servers). It is not like MySQL's market was any where near > saturated before 4.0. In fact, one of the rules in business is if > something is working then continue doing that thing. Don't break it. And > take incremental steps away from current success. > > There is no way you launch into new markets without having growing pains. > If you look at the historical record, you will see that MySQL kept on developing 3.22 until (and even a little beyond) when 3.23 was declared stable. Nobody pretends that 4.0 is stable yet, so I would imagine that active development will continue on 3.23 for some time. I'm sure the MySQL developers would appreciate your help in maintaining the current, stable 3.23 branch. I understand your concerns -- the company I used to work for took a long time to finally convert from 3.22 to 3.23. In fact, there are people on this mailing list still using 3.22. Perhaps you could contribute to the main 3.23 branch until 4.0 becomes stable, and then perhaps make a deal with MySQL to continue the active development on that branch for them. There are a lot of MySQL 3.23 users, and I would just like to see them all benefit from both your changes and the MySQL developers changes. Forking the code just makes that more difficult, as then a choice must be made as to which benefits you'd like to have. Anyway, as it's GPL'ed, you can pretty much do whatever you want, and my opinion is just one opinion among many, I'm sure! Good luck with whatever you do, but one way or another I hope we can all share the benefits of your changes. If you do fork, perhaps it would be appropriate to post announcements of new versions on this list? Steve Meyers --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
