> You've already stated your lack of belief in the reliability of deadlines,
> so what did you expect? If someone had responded with "4.1 will be done on
> 5/1/2002" you'd respond that the only way that would happen would be if it
> were horribly buggy or lacked "critical" features -- if you hold
> Fra: Heikki Tuuri [mailto:[EMAIL PROTECTED]]
> Sendt: 16. april 2002 09:52
> MySQL AB wants to satisfy as many users as possible. That means
> there may be
> more than one language available for writing stored procedures.
>
> For example, many mainstream databases currently support both Java an
Innobase Oy
- Original Message -
From: "Carsten Gehling" <[EMAIL PROTECTED]>
To: "Heikki Tuuri" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, April 16, 2002 10:40 AM
Subject: SV: MySQL and stored procedures -> v4.1 :(
> > Fra: Heikki
> Fra: Heikki Tuuri [mailto:[EMAIL PROTECTED]]
> Sendt: 16. april 2002 02:15
> I can disclose that there is actually some progress being made in stored
> procedures + triggers.
Ahh could you perhaps disclose a little more? :-) There's been a great
discussion on the choice of language, and I'm su
AM
Subject: RE: MySQL and stored procedures -> v4.1 :(
> > > When it's ready.
> >
> > That's a tautological answer.
>
> You've already stated your lack of belief in the reliability of deadlines,
> so what did you expect? If someone had responded
> > When it's ready.
>
> That's a tautological answer.
You've already stated your lack of belief in the reliability of deadlines,
so what did you expect? If someone had responded with "4.1 will be done on
5/1/2002" you'd respond that the only way that would happen would be if it
were horribly bu
> > But I did ask for a release date of version 4.1.
>
> When it's ready.
That's a tautological answer.
> > A nice thing with a stored procedure is that you can lower the load
> > impact made by heavy queries on the database by using cursors to soften
> > the performance hit they are likely to
> But I did ask for a release date of version 4.1.
When it's ready.
> A nice thing with a stored procedure is that you can lower the load
> impact made by heavy queries on the database by using cursors to soften
> the performance hit they are likely to make - e.g. make the query behave
> like a
> > I'll trust a MySQL alpha release before the final production releases of
> > most vendors. In fact, we're using 4.0.1 in our production
> environment with
> > great success.
> Its your system, and if you think it worth the risc, it is of course you
> decision to do so to, ;) but I would never
Did I ask for optimization tips?
Nope. ;)
But I did ask for a release date of version 4.1.
> -Original Message-
> From: Land, Christopher
> Sent: Friday, April 12, 2002 11:18 PM
> To: Jon Frisby; Mysql List
> Subject: RE: MySQL and stored procedures -> v4.1 :(
&g
> > Checked my own version and found it to be "Ver 11.16 Distrib 3.23.49".
> >
> > He, version 11??? Quit confused, but after a sanity check with reality
> > I realized I must be using version 3.23. Anyhow, check the status of
> > next version and found out that version 4.0 is in alpha mode...
>
EMAIL PROTECTED]]
Sent: Friday, April 12, 2002 11:43 AM
To: Mysql List
Subject: RE: MySQL and stored procedures -> v4.1 :(
> Checked my own version and found it to be "Ver 11.16 Distrib 3.23.49".
>
> He, version 11??? Quit confused, but after a sanity check with reality
&
> Checked my own version and found it to be "Ver 11.16 Distrib 3.23.49".
>
> He, version 11??? Quit confused, but after a sanity check with reality
> I realized I must be using version 3.23. Anyhow, check the status of
> next version and found out that version 4.0 is in alpha mode...
The "Ver 11.1
Installed MySQL and about the first thing I tried to create was a stored
procedure - failed.
Found out fairly quickly with a text search in the manual that stored
procedures is not to be introduced until version 4.1.
Checked my own version and found it to be "Ver 11.16 Distrib 3.23.49".
He, ver
14 matches
Mail list logo
