On Friday 22 February 2002 06:26 am, Arjen Lentz wrote: > Hi Alec, > > On Fri, 2002-02-22 at 18:59, [EMAIL PROTECTED] wrote: > > > Is there a timeline/status for 4.x functionality available? > > > I would like to use MySQL 4.x, however, I'm looking for some of the > > > highly requested functionality (ie; subselects, SP's, triggers and > > > Views) and would like to know where/when in the sequence of things todo > > > does everything fall into place. This will help me plan my > > > development effort as well since I don't need everything at once. > > There certainly is a general timeline... have a look at various points > in the online manual (http://www.mysql.com/doc/) to see what the > priorities are and will be. > As for exact dates: "it will be ready when it's ready." > Some may not like that response, but it's honest. As you know, with > MySQL we prefer to do a solid implementation rather than a quick hack. >
This is the excerpt I found from the docs and I"m having difficulty trying to figure out what "within a couple of months" is relative to. I was wondering if there is some clearer date with regards to the upcoming beta: "The rollout of MySQL Server 4.0 will come in several steps, with the first version labelled 4.0.0 already containing most of the new features. Additional features will be incorporated into MySQL 4.0.1, 4.0.2 onwards; very probably within a couple of months, MySQL 4.0 will be labelled beta. Further new features will then be added in MySQL 4.1, which is targeted for alpha release in early 2002. " > > I would like to second this request. I *really* want the replication > > failover functionality targeted for "4.x". In fact, if it isn't going to > > arrive by, say, midsummer, I will have to develop my own failover > > solutions. Which, obviously, I don't want to do - I have this aversion to > > reinventing wheels, and I have this nasty feeling that the MySQL teams > > wheels would be rounder than mine. So some indication of the timescales > > would be really useful. I certainly don't need exact dates, and I know > > all about the delays in development - but some indiciation would be > > really helpful and could save me a lot of work. > > If you have a commercial interest in speeding up a particular part of > our planned development, this is certainly something that can be talked > about. As you may know, the original replication was done as a > 'sponsored' project. One company needed it, and provided the funds to > allow us to allocate manpower for doing it. Now, it benefits many more! > > MySQL's development path is not for sale, but like any company we have > to accept certains limit in our human and financial resources. > Sponsoring a particular part can in cases such as these allow for faster > development, provided of course that technical prerequisites are met; > naturally the rule about solid implementations still applies. > > > To get you (and others) thinking along an interesting track.... > sponsoring need not be limited to a single company making a large > targeted contribution. It could very well be multiple small(er) > companies that have a similar need. > The question is simply how fast you need a certain feature, and what it > will save you to have it that fast, and/or gain you by having it help > your business. That knowledge would allow you to invest (part of) those > savings into making sure that it does happen. > > > Regards, > Arjen. --------------------------------------------------------------------- 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
