On Sunday 24 February 2002 06:26 pm, Arjen Lentz wrote: > Hi Anthony, > > On Fri, 2002-02-22 at 23:43, Anthony W. Marino wrote: > > > 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. " > > For MySQL Server, an alpha becomes a beta when 1) all features scheduled > for that version have been added and 2) no disastrous new bugs are being > reported (generally regarding the new features, but of course it is > possible that new code also inadvertantly affects the behaviour of old > code). > > So, it is not a completely new separate version or anything like that, > it just signifies the development status. It is very dependent on the > feedback we get (i.e. the problems that may be found) and therefore > there can't be an absolute timeline. The "within a few months" is just a > ballpark figure, relative to the initial alpha release of a sub-version > (like 4.0.0). > > If you keep an eye on the mailing list and the change log for 4.0.x, you > can decide for yourself if the server is stable enough for you. > > > I hope this clarifies the issue a bit? > I am a bit unsure about exactly what you are looking for... if you want > solid code, there can't be an absolute timeline with fixed release > dates. I am sure everybody prefers good code. Yet people also keep > asking about specific dates for version releases... I suppose it's > natural, we're all eager and curious, but maybe you can give me an > additional explanation? > I DO understand that the BETA becomes available when ALL slated features have made it into the alpha and with some certainity of stability. My concern is in knowing when some of these features (ie; subselects, triggers, sp's and etc) will make it into the alpha so that I can coordinate my coding efforts around them. Don't forget, the db isn't the only part of many software projects. And the more uncertainity that we have about the timing of features/functionality availability which our (my) progam and/or code might need to rely on, it's quite possible that almost everything will be ready for nothing or nothing will be ready for everything.
I DO appreciate the GREAT work that's going on with MySQL, however, I'm also looking at other products that already have the above such as PostgreSQL and Firebird (InterBase Opensource) and trying to measure the pros/cons of all three, however, it would make things ALOT easier if I new when the above features would be available. Regards and Thank You, Anthony > 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
