>What's so tough >about making a patch to 3.23 and sending it to the MySQL developers?
3.23 will not the most current cvs soon I assume. Or does MySQL actively support, debug, fix, and go back and maintain older releases? > I >also doubt that anyone working on the new fork will be able to convince >thousands of web hosts to replace MySQL with 'WSSQL', Well I could own a growing host as well. For now, I gave all my users to let someone else run it: http://coolpagehosting.com I think there are several thousand users already and hasn't be up long. But the number of servers running MySQL is very small compared to the number of web sites. So the race is wide open still. If someone else were to present a better option to the millions of users, this could transform into popularity on the backend. To keep from getting too angry at me, think of these things in the context of the alternative. Microsoft .Net is coming. Take a look at the new toolbar in Hotmail, just to get an idea of how Microsoft is going to convert their 97% market share on the desktop and browser, into same on the backend. >particularly if >they start changing standard MySQL behavior and breaking existing >applications. Ditto the above points. > However, if Shelby manages to speed up MySQL by coding >assembly for every platform MySQL runs on, than I for one will be >impressed ; ) No comment. > >> 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. >Oddly enough, the 4.0 releases won't change MySQL's behavior, unless of >course you are utilizing the new features. The mysql.com announcement about 4.0 disagrees with your assertion. > Your changes DO affect its >behavior, What changes? I did not make any yet. Are you dragging information from my other thread into this one? > and may introduce new bugs into previously stable and >well-tested code. Any changes by any one can do this. What is your point? > Also, I'm not sure what the 'costs' of upgrading to >version 4.0 might be. The 'cost' of new features? Or maybe a few extra >megs of disk space? Time? Hassle? Compile issues? Etc..... >I am not sure what this is supposed to mean, but I think that MySQL is a >great example of a focused open-source project. It has clearly stated >goals (speed, ease of use), and while new versions may add new features, >they don't slow the database down or make it more difficult to use. I agree. That doesn't mean though that the improvements schedule is meeting the needs of everyone who is already a user. Some users may have different priorities. Please respect our right to state our opinion and have discussions to determine whether there is enough reason to fork or not. It is a discovery process. I for one, do not have a closed-mind about it. >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? These are very different numbers and very important distinctions. But I don't want to have this debate with you. If you aren't interested in this project, then kindly stay off this thread, or at least kindly do not take personal stabs at me. > most of the other items on the to do list have been discussed >extensively here as well. I will grant you that I was not here on this list when those discussions occurred. > 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). 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. (Please keep your replies off of the personal level and innuedo attacks) > > >Ben > > >--------------------------------------------------------------------- >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 > --------------------------------------------------------------------- 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
