BTW: in the early MySQL years we had many choices about being compatible with our current users or make it easier for new users. And since we where ambitious and belived that the new users where many we prioritised them.
And clearly we missed this thing (but unless we had done that the list of broken things like this could have been looonger...). So my hope is that drizzle also concentrate on getting it right and tries to help compatibility by good messages (like jeremyz proposed). I do hope drizzle gets much better error messages than MySQL since MySQLs error messages has been a pain for me since the very beginning... Lots of times where he spend time scratching my head a good error messsage pointing you in the right direction may cut a looong sessions to a single aha. I think MySQL still says corrupted table ... when the disk runs out while creating temp tables. Horrible since it will make the non informed took for stuff that does not exist... /David On Mon, 2008-12-08 at 11:58 -0800, Eric Bergen wrote: > A few weeks of confusion and relearning to the core audience now is > worth decades of confusing most new users. It may not be as important > as the other work going on in drizzle but I think it's worth > discussing. I wish someone would have sat down and fixed this issue in > mysql a decade ago so we wouldn't even be discussing it now. It may > have been painful for a release but would have long since been > fogoten. Now we still deal with it today. > > On Mon, Dec 8, 2008 at 11:33 AM, Sean Kelly <[email protected]> wrote: > > -5 extremely unimportant and possibly confusing to the core audience > > that may migrate earliest from mysqld to drizzled > > > > > > On Mon, Dec 8, 2008 at 9:39 AM, Martin MC Brown <[email protected]> > > wrote: > >> > >> On 8 Dec 2008, at 17:29, Eric Herman wrote: > >> > >>> Jay Pipes wrote: > >>>> > >>>> Added a Blueprint: > >>>> > >>>> https://blueprints.launchpad.net/drizzle/+spec/usability-cli-port-specification > >>>> I've > >>>> left the definition in "Discussed" status, and appended the task to the > >>>> Low > >>>> Hangin Fruit milestone, which is the ongoing "fix it if you can find > >>>> time" > >>>> milestone: > >>>> https://blueprints.launchpad.net/drizzle/+milestone/low-hanging-fruit > >>>> Please reply a +1 or -1 on whether this small usability change is a good > >>>> idea. > >>> > >>> +1 > >> > >> > >> +1 > >> > >> I'd prefer some higher number than one to indicate importance, but... > >> > >> MC > >> > >> > >> -- > >> Martin MC Brown, Technical Writer > >> Database Technology Group, Sun Microsystems > >> http://sun.com | http://mysql.com > >> Phone: x18435/+44 247 669 8435 Skype: mcmcslp > >> > >> > >> > >> > >> > >> _______________________________________________ > >> Mailing list: https://launchpad.net/~drizzle-discuss > >> Post to : [email protected] > >> Unsubscribe : https://launchpad.net/~drizzle-discuss > >> More help : https://help.launchpad.net/ListHelp > >> > > > > _______________________________________________ > > Mailing list: https://launchpad.net/~drizzle-discuss > > Post to : [email protected] > > Unsubscribe : https://launchpad.net/~drizzle-discuss > > More help : https://help.launchpad.net/ListHelp > > > > > _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
