merge

@subheading Web Servers with @strong{MySQL} Tools

@table @asis

@item @uref{http://bourbon.netvision.net.il/mysql/mod_auth_mysql/}

An Apache authentication module.

@item @uref{ftp://ftp.kcilink.com/pub/}

mod_auth_mysql, An Apache authentication module.

@item @uref{http://www.roxen.com/}

The Roxen Challenger Web server.

@email{myodbc-subscribe@@lists.mysql.com} or

@email{myodbc-unsubscribe@@lists.mysql.com}.

If you can't get an answer for your questions from the mailing list, one

option is to pay for support from @strong{MySQL AB}, which will put you

in direct contact with @strong{MySQL} developers. @xref{Support}.

The following table shows some @strong{MySQL} mailing in other languages than

English.  Note that these are not operated by @strong{MySQL AB}, so we can't

guarantee the quality on these.

@itemize @minus

@item

You link a part of the of @strong{MySQL} that has a GPL Copyright to a

program that is not free software (embedded usage of the @strong{MySQL}

server).  In this case your application would also become GPL through the

clause in the GPL license that acts as a virus.  By licensing @strong{MySQL} 

from us under a commercial license you will avoid this problem.

You link a program, that is not free software, with code from the

@strong{MySQL} server or clients that has the GPL copyright. This

happens for example when you use @strong{MySQL} as an embedded server

in your applications or when you add not free extensions to the

@strong{MySQL} server.  In this case your application/code would also

become GPL through the GPL license that acts as a virus.  By licensing

@strong{MySQL} server from @strong{MySQL AB} under a commercial

license you will avoid this problem.

See @uref{http://www.gnu.org/copyleft/gpl-faq.html}.

@item

You have a commercial application that ONLY works with @strong{MySQL}

and ships the application with the @strong{MySQL} server.  This is

A collection of our standard configure scripts is located in the

@file{BUILD/} subdirectory.  If you are lazy, you can use

@file{BUILD/compile-pentium-debug}.  It will actually work on a lot of

non-x86 machines despite its name.

@file{BUILD/compile-pentium-debug}. To compile on a different architecture,

modify the script removing flags that are Pentium-specific.

@item

When the build is done, run @code{make install}.  Be careful with this

open_files_limit=8192

@end example

The above should allow @strong{MySQL} to create up to 8192 connections + files.

The above should allow @strong{MySQL} to create up to 8192 connections/files.

The @code{STACK_SIZE} constant in LinuxThreads controls the spacing of thread

stacks in the address space.  It needs to be large enough so that there will

be stored in the same byte that is used to mark if a key is @code{NULL}.)

@item

If you specify a @code{SELECT} after the @code{CREATE STATEMENT},

If you specify a @code{SELECT} after the @code{CREATE} statement,

@strong{MySQL} will create new fields for all elements in the

@code{SELECT}.  For example:

           TYPE=MyISAM SELECT b,c from test2;

@end example

This will create a @code{MyISAM} table with 3 columns.  Note that the

table will automatically be deleted if any errors occur while copying

data into the table.

This will create a @code{MyISAM} table with three columns, a, b, and c.

Notice that the columns from the @code{SELECT} statement are appended to

the right side of the table, not overlapped onto it.  Take the following

example:

@example

mysql> select * from foo;

+---+

| n |

+---+

| 1 |

+---+           

mysql> create table bar (m int) select n from foo;

Query OK, 1 row affected (0.02 sec)

Records: 1  Duplicates: 0  Warnings: 0

mysql> select * from bar;

+------+---+

| m    | n |

+------+---+

| NULL | 1 |

+------+---+

1 row in set (0.00 sec)                           

@end example

For each row in table @code{foo}, a row is inserted in @code{bar} with

the values from @code{foo} and default values for the new columns.

If any errors occur while copying the data to the table, it will 

automatically be deleted. 

To ensure that the update log/binary log can be used to re-create the

original tables, @strong{MySQL} will not allow concurrent inserts during

update a row or find a row by key (this is VERY unlikely to happen if a

normal check has succeeded!).

Some things reported by check table, can't be corrected automaticly:

@itemize @bullet

@item

@code{Found row where the auto_increment column has the value 0}.

This means that you have in the table a row where the

@code{auto_increment} index column contains the value 0.

(It's possible to create a row where the auto_increment column is 0 by

explicitely setting the column to 0 with an @code{UPDATE} statement)

This isn't an error in itself, but could cause trouble if you decide to

dump the table and restore it or do an @code{ALTER TABLE} on the

table. In this case the auto_increment column will change value,

according to the rules of auto_increment columns, which could cause

problems like a duplicate key error.

To get rid of the warning, just execute an @code{UPDATE} statement

to set the column to some other value than 0.

@end itemize

@findex BACKUP TABLE

@node BACKUP TABLE, RESTORE TABLE, CHECK TABLE, Reference

@section @code{BACKUP TABLE} Syntax

or  INSERT [LOW_PRIORITY | DELAYED] [IGNORE]

        [INTO] tbl_name

        SET col_name=expression, col_name=expression, ...

or  INSERT [LOW_PRIORITY] [IGNORE] [INTO] tbl_name

        SELECT ...

@end example

an extension, the extension number of the log file will be incremented

by one relative to the previous file.  If you have used an extension in

the file name, @strong{MySQL} will close and reopen the update log file.

@xref{Update log}.

@xref{Update log}. This is the same thing as sending the @code{SIGHUP}

signal to the @code{mysqld} server.

@item @code{PRIVILEGES} @tab Reloads the privileges from the grant tables in

the @code{mysql} database.

@item @code{TABLES WITH READ LOCK} @tab Closes all open tables and locks all tables for all databases with a read until one executes @code{UNLOCK TABLES}. This is very convenient way to get backups if you have a file system, like Veritas,that can take snapshots in time.

@item @code{STATUS} @tab Resets most status variables to zero.

@item @code{STATUS} @tab Resets most status variables to zero. This is something one should only use when debugging a query.

@end multitable

You can also access each of the commands shown above with the @code{mysqladmin}

utility, using the @code{flush-hosts}, @code{flush-logs}, @code{reload},

or @code{flush-tables} commands.

Take also a look at the @code{RESET} command used with

replication. @xref{Replication SQL}.

@cindex @code{mysqladmin}

@findex KILL

@node KILL, SHOW, FLUSH, Reference

@item @code{net_read_timeout}

Number of seconds to wait for more data from a connection before aborting

the read.  Note that when we don't expect data from a connection, the timeout

is defined by @code{write_timeout}.

is defined by @code{write_timeout}. See also @code{slave_read_timeout}.

@item @code{net_retry_count}

If a read on a communication port is interrupted, retry this many times

concerned about people being able to see what databases other users

have. See also @code{safe_show_databases}.

@item @code{slave_read_timeout}

Number of seconds to wait for more data from a master/slave connection

before aborting the read.

@item @code{slow_launch_time}

If creating the thread takes longer than this value (in seconds), the

@code{Slow_launch_threads} counter will be incremented.

@item TIMESTAMP = timestamp_value | DEFAULT

Set the time for this client.  This is used to get the original timestamp if

you use the update log to restore rows.

you use the update log to restore rows.  @code{timestamp_value} should be a

UNIX Epoch timestamp, not a @strong{MySQL} timestamp.

@item LAST_INSERT_ID = #

Set the value to be returned from @code{LAST_INSERT_ID()}. This is stored in

@multitable @columnfractions .30 .70

@item @code{innodb_data_home_dir} @tab 

The common part of the directory path for all innobase data files.

The common part of the directory path for all InnoDB data files.

@item @code{innodb_data_file_path} @tab 

Paths to individual data files and their sizes. The full directory path

to each data file is acquired by concatenating innodb_data_home_dir to

@item @strong{Option} @tab @strong{Description}

@item @code{log-bin=filename} @tab

Write to a binary update log to the specified location. Note that if you

give it a parameter with an extension

(for example, @code{log-bin=/mysql/logs/replication.log} ) versions up to 3.23.24

will not work right during replication if you do @code{FLUSH LOGS} . The

problem is fixed in Version 3.23.25. If you are using this kind of log name,

@code{FLUSH LOGS} will be ignored on binlog. To clear the log, run

give it a parameter with an extension (for example,

@code{log-bin=/mysql/logs/replication.log} ) versions up to 3.23.24 will

not work right during replication if you do @code{FLUSH LOGS} . The

problem is fixed in Version 3.23.25. If you are using this kind of log

name, @code{FLUSH LOGS} will be ignored on binlog. To clear the log, run

@code{FLUSH MASTER}, and do not forget to run @code{FLUSH SLAVE} on all

slaves. In Version 3.23.26 and in later versions you should use @code{RESET MASTER}

and @code{RESET SLAVE}

slaves. In Version 3.23.26 and in later versions you should use

@code{RESET MASTER} and @code{RESET SLAVE}

@item @code{log-bin-index=filename} @tab

Because the user could issue the @code{FLUSH LOGS} command, we need to

@code{replicate-ignore-table=foo%.bar%} - will not upates to tables in all databases that start with foo and whose table names

start with bar)

@item @code{replicate-ignore-db=database_name} @tab

Tells the slave thread to not replicate to the specified database. To

specify more than one database to ignore, use the directive multiple

@code{replicate-wild-do-table=db_name.%}

(Example: @code{replicate-do-db=some_db})

@item @code{log-slave-updates} @tab

Tells the slave to log the updates from the slave thread to the binary

log. Off by default. You will need to turn it on if you plan to

@item @code{skip-slave-start} @tab

Tells the slave server not to start the slave on the startup.  The user

can start it later with @code{SLAVE START}.

@item @code{slave_read_timeout=#}

Number of seconds to wait for more data from the master before aborting

the read.

@end multitable

@cindex SQL commands, replication

@item

If you have decided you can skip the next query, do

@code{SET SQL_SLAVE_SKIP_COUNTER=1; SLAVE START;} to skip a query that

does not use auto_increment, last_insert_id or timestamp, or

@code{SET SQL_SLAVE_SKIP_COUNTER=2; SLAVE START;} otherwise

does not use auto_increment, or last_insert_id  or

@code{SET SQL_SLAVE_SKIP_COUNTER=2; SLAVE START;} otherwise. The reason

auto_increment/last_insert_id queries are different is that they take

two events in the binary log of the master.

@item

If you are sure the slave started out perfectly in sync with the master,

and no one has updated  the tables involved outside of slave thread,

@code{table_cache} is related to @code{max_connections}.  For example,

for 200 concurrent running connections, you should have a table cache of

at least @code{200 * n}, where @code{n} is the maximum number of tables

in a join.

in a join.  You also need to reserve some extra file descriptors for

temporary tables and files.

The cache of open tables can grow to a maximum of @code{table_cache}

(default 64; this can be changed with the @code{-O table_cache=#}

Added option @code{--warnings} to @code{mysqld}. Now @code{mysqld}

only prints the error @code{Aborted connection} if this option is used.

@item

Fixed problem with @code{--low-priority-updates} and @code{INSERT}'s.

@item

Fixed bug in slave thread when under some rare circumstances it could

get 22 bytes ahead on the offset in the master

@item

Added @code{slave_wait_timeout} for replication.

@item

Fixed problem with @code{UPDATE} and BDB tables.

@item

Fixed hard bug in BDB tables when using key parts.

@item

Fixed problem when using the @code{GRANT FILE ON database.* ...}; Previously

we added the @code{DROP} privilege for the database.

@item

Fixed that @code{DELETE FROM table_name ... LIMIT 0} and

@code{UPDATE FROM table_name ... LIMIT 0} doesn't delete/update anything.

@item

@code{CHECK TABLE} now checks if an auto_increment column contains the value 0.

@item

Sending a @code{SIGHUP} to @code{mysqld} will now only flush the logs,

not reset the replication.

@item

Fixed parser to allow floats of type @code{1.0e1} (no sign after @code{e}).

@item

Option @code{--force} to @code{myisamchk} now also updates states.

@item

Fixed a bug when using @code{COUNT(DISTINCT)} with @code{LEFT JOIN} and

there wasn't any matching rows.

@item

Removed all documentation referring to the @code{GEMINI} table

type. @code{GEMINI} is not released under an Open Source license.

@end itemize

@node News-3.23.39, News-3.23.38, News-3.23.40, News-3.23.x

running not completed multi-statement transactions. (The transaction

will probably be ignored).

@item

@code{ANALYZE TABLE}, @code{OPTIMIZE TABLE} and @code{REPAIR TABLE} may

cause problems on tables for which you are using @code{INSERT DELAYED}.

@item

Doing a @code{LOCK TABLE ..} and @code{FLUSH TABLES ..} doesn't

guarantee that there isn't a half-finished transaction in progress on the

table.

@item

BDB tables are a bit slow to open from this. If you have many BDB tables

in a database, it will take a long time to use the @code{mysql} client

on the database if you are not using the @code{-A} option or if you are

using @code{rehash}. This is especially notable when you have a big table

BDB tables are a bit slow to open. If you have many BDB tables in a

database, it will take a long time to use the @code{mysql} client on the

database if you are not using the @code{-A} option or if you are using

@code{rehash}. This is especially notable when you have a big table

cache.

@item

and import data. We should as an intermediate solution change @code{NaN} to

@code{NULL} (if possible) and @code{-Inf} and @code{Inf} to the

Minimum respective maximum possible @code{double} value.

@item

@code{LIMIT} on negative numbers are treated as big positive numbers.

@end itemize

The following are known bugs in earlier versions of @strong{MySQL}:

Make it possible to specify @code{long_query_time} with a granularity

in microseconds.

@item

Add a configurable prompt to the @code{mysql} command line client, with

options like database in use, time and date...

@item

Add range checking to @code{MERGE} tables.

@item

Link the @code{myisampack} code into the server.

	u_int32_t dlen;			/* RO: get/put record length. */

	u_int32_t doff;			/* RO: get/put record offset. */

	void	*app_private;		/* Application-private handle. */

#define	DB_DBT_ISSET	0x001		/* Lower level calls set value. */

#define	DB_DBT_MALLOC	0x002		/* Return in malloc'd memory. */

#define	DB_DBT_PARTIAL	0x004		/* Partial put/get. */

        AC_MSG_RESULT(yes)

        AC_DEFINE(LIBWRAP)

        AC_DEFINE(HAVE_LIBWRAP)

        WRAPLIBS="-L$with_libwrap/lib -lwrap",

	if test "$with_libwrap" != "yes"; then

	    WRAPLIBS="-L${with_libwrap}/lib"

	fi

	WRAPLIBS="${WRAPLIBS} -lwrap",

        AC_MSG_RESULT(no)

        CPPFLAGS=${_cppflags} LDFLAGS=${_ldflags}),

      CPPFLAGS=${_cppflags} LDFLAGS=${_ldflags})

    echo "Adding fix for interrupted reads"

    CXXFLAGS="$CXXFLAGS -DMYSQLD_NET_RETRY_COUNT=1000000"

    ;;

  *netbsd*)

    echo "Adding flag -Dunix"

    CFLAGS="$CFLAGS -Dunix"

    CXXFLAGS="$CXXFLAGS -Dunix"

    OVERRIDE_MT_LD_ADD="\$(top_srcdir)/mit-pthreads/obj/libpthread.a"

    ;;

  *bsdi*)

    echo "Adding fix for BSDI"

    CFLAGS="$CFLAGS -D__BSD__ -DHAVE_BROKEN_REALPATH"

then

  my_save_LIBS="$LIBS"

  AC_CHECK_LIB(c_r,strtok_r)

  if test "$with_osf32_threads" = "yes" -o "$target_os" = "FreeBSD" -o "$target_os" = "freebsd" 

  then

    LIBS="$my_save_LIBS"

  fi

  case "$with_osf32_threads---$target_os" in

    # Don't keep -lc_r in LIBS; -pthread handles it magically

    yes---* | *---freebsd* ) LIBS="$my_save_LIBS" ;;

  esac

  AC_CHECK_FUNCS(strtok_r pthread_init)

else

  AC_CHECK_FUNCS(strtok_r)

header, even if we're not building with Berkeley DB.

Obviously, if this file *is* used, it'll break and hopefully we can find

out why this file was generated by $(top_srcdir)/configure instead of

out why this file was generated by ${top_srcdir}/configure instead of

the real db.h.

If you run into some problems because of this file, please use mysql_bug

    AC_DEFINE(HAVE_mit_thread)

    MT_INCLUDES="-I\$(top_srcdir)/mit-pthreads/include"

    AC_SUBST(MT_INCLUDES)

    if test -n "$OVERRIDE_MT_LD_ADD"

    then 

      MT_LD_ADD="$OVERRIDE_MT_LD_ADD"

    else

      MT_LD_ADD="-L \$(top_srcdir)/mit-pthreads/obj/ -lpthread"

    fi

    AC_SUBST(MT_LD_ADD)

    LIBS="$MT_LD_ADD $LIBS"

    echo ""

    echo "Configuring MIT Pthreads"

    # We will never install so installation paths are not needed.

    (cd mit-pthreads; sh ./configure)

    echo "End of MIT Pthreads configuration"

    echo ""

    LIBS="$MT_LD_ADD $LIBS"

  fi

fi

AC_SUBST(sql_server_dirs)

extern ulong max_write_lock_count;

extern my_bool thr_lock_inited;

extern enum thr_lock_type thr_upgraded_concurrent_insert_lock;

typedef struct st_thr_lock_data {

  pthread_t thread;

static int detzcode(const char * codep)

{

	long result;

	int result;

	int	i;

	result = 0;