Updated text on stored procedures and triggers.

performance because the query has to be parsed only once, and less information

needs to be sent between the server and the client. You can also raise the

conceptual level by having libraries of functions in the server.

Unfortunately, stored procedures are not very standardised yet.

A trigger is a stored procedure that is invoked when a particular event

occurs.  For example, you can install a stored procedure that is triggered

deletes the corresponding customer from a customer table when all his

transactions are deleted.

The planned update language will be able to handle stored procedures, but

without triggers. Triggers usually slow down everything, even queries for

which they are not needed. To see when MySQL will get stored procedures,

see @ref{TODO}.

The planned update language will be able to handle stored procedures.

Our aim is to have stored procedures implemented in MySQL 4.1.

We are also looking at triggers.

@node ANSI diff Foreign Keys, ANSI diff Views, ANSI diff Triggers, Differences from ANSI

@item

Fix sorting and grouping of @code{BLOB} columns (partly solved now).

@item

Stored procedures.  This is currently not regarded to be very

important as stored procedures are not very standardised yet.

Another problem is that true stored procedures make it much harder for

the optimiser and in many cases the result is slower than before

We will, on the other hand, add a simple (atomic) update language that

Stored procedures.

@item

Add a simple (atomic) update language that

can be used to write loops and such in the MySQL server.

@item

Change to use semaphores when counting threads.  One should first implement