manual.texi API's -> APIs

* ODBC and last_insert_id::     How to get the value of an @code{AUTO_INCREMENT} column in ODBC

* MyODBC bug report::           Reporting problems with MyODBC

Using @code{MySQL} with some common programs

Using @strong{MySQL} with some common programs

* Apache::                      Using @strong{MySQL} with Apache

Sendmail and Procmail}

@end itemize

@subheading Using @code{MySQL} with other programs

@subheading Using @strong{MySQL} with other programs

@itemize @bullet

@item

because we view this a linking even if it is done over the network.

@item

You have a distribution of @code{MySQL} and you don't provide the

You have a distribution of @strong{MySQL} and you don't provide the

source code for your copy of the @strong{MySQL} server, as defined in

the GPL license.

@end itemize

All ISPs that wants to keep themself up to date should subscribe

to our announce mailing list so that they can be aware of fatal issues

that may be relevant for their @code{MySQL} installations.

that may be relevant for their @strong{MySQL} installations.

Note that if the ISP doesn't have a license for @code{MySQL},

Note that if the ISP doesn't have a license for @strong{MySQL},

they should give their customers at least read access to the source of

the @code{MySQL} installation so that their customer can verify that

the @strong{MySQL} installation so that their customer can verify that

it's patched correctly.

@node Web server,  , ISP, Licensing examples

commands and extensions in most alpha releases.  Active development that

may involve major code changes can occur on an alpha release, but everything

will be tested before doing a release.  There should be no known bugs in any

@code{MySQL} release.

@strong{MySQL} release.

@item

@code{beta} means that all new code has been tested. No major new

@end itemize

If you are using gcc and have problems with loading @code{UDF} functions

into @code{MySQL}, try adding @code{-lgcc} to the link line for the

into @strong{MySQL}, try adding @code{-lgcc} to the link line for the

@code{UDF} function.

If you would like @strong{MySQL} to start automatically, you can copy

@node Linux-Ia64,  , Qube2, Linux

@subsubsection Linux Ia64 notes

To get @code{MySQL} to compile on Linux Ia64, we had to do the following

To get @strong{MySQL} to compile on Linux Ia64, we had to do the following

(we assume that this will be easier when next gcc version for ia64 is

released).

port to ``sco 3.2v4.2''.

For the moment the recommended compiler on OpenServer is gcc 2.95.2. With this

you should be able to compile @code{MySQL} with just:

you should be able to compile @strong{MySQL} with just:

@example

CC=gcc CXX=gcc ./configure ... (options)

now a function that takes @code{MYSQL_RES*} as an argument. You should now

use @code{mysql_field_count()} instead.

@item

In @code{MySQL} 3.22, the output of @code{SELECT DISTINCT ...} was

In @strong{MySQL} 3.22, the output of @code{SELECT DISTINCT ...} was

almost always sorted.  In 3.23, you must use @code{GROUP BY} or

@code{ORDER BY} to obtain sorted output.

@item

The following mostly apply only for @code{ISAM}, @code{MyISAM} and

@code{HEAP} tables; If you only use transaction safe tables (@code{BDB}

tables) in an a update you can do @code{COMMIT} and @code{ROLLBACK} also

with @code{MySQL}.  @xref{COMMIT}.

with @strong{MySQL}.  @xref{COMMIT}.

The problem with handling @code{COMMIT}-@code{ROLLBACK} efficiently with

the above table types would require a completely different table layout

@item

Try to find out what is wrong with your DNS server and fix this.

@item

Specify IPs instead of hostnames in the @code{MySQL} privilege tables.

Specify IPs instead of hostnames in the @strong{MySQL} privilege tables.

@item

Start mysqld with @code{--skip-name-resolve}.

@item

@code{NATIONAL CHAR} (short form @code{NCHAR}) is the ANSI SQL way to

define that a CHAR column should use the default CHARACTER set.  This is

default in @code{MySQL}.

default in @strong{MySQL}.

@code{CHAR} is a shorthand for @code{CHARACTER}.

returns @code{0}.  @code{RLIKE} is a synonym for @code{REGEXP}, provided for

@code{mSQL} compatibility. Note: Because @strong{MySQL} uses the C escape

syntax in strings (e.g., @samp{\n}), you must double any @samp{\} that you

use in your @code{REGEXP} strings.  In @code{MySQL} 3.23.4

use in your @code{REGEXP} strings.  In @strong{MySQL} 3.23.4,

@code{REGEXP} is case insensitive for normal (not binary) strings.

@example

positive floating point number. Zero relevance means no similarity.

For @code{MATCH ... AGAINST()} to work, a @strong{FULLTEXT} index

must be created first. @xref{CREATE TABLE, , @code{CREATE TABLE}}.

@code{MATCH ... AGAINST()} is available in @code{MySQL} 3.23.23 or later.

@code{MATCH ... AGAINST()} is available in @strong{MySQL} 3.23.23 or later.

For details and usage examples see @xref{MySQL full-text search}.

@end table

           GROUP BY id,val ORDER BY val;

@end example

In @code{MySQL} 3.23 you can do:

In @strong{MySQL} 3.23 you can do:

@example

mysql> SELECT id,FLOOR(value/100) FROM tbl_name ORDER BY RAND();

normally be @code{OK}.  If you don't get @code{OK}, or @code{Not

checked} you should normally run a repair of the table. @xref{Table

maintenance}. @code{Not checked} means that the table the given @code{TYPE}

told @code{MySQL} that there wasn't any need to check the table.

told @strong{MySQL} that there wasn't any need to check the table.

The different check types stand for the following:

start @code{mysqld} with @code{--skip-bdb} o not waste memory for this cache.

@item @code{concurrent_inserts}

If @code{ON} (the default), @code{MySQL} will allow you to use @code{INSERT}

If @code{ON} (the default), @strong{MySQL} will allow you to use @code{INSERT}

on @code{MyISAM} tables at the same time as you run @code{SELECT} queries

on them.  You can turn this option off by starting mysqld with @code{--safe}

or @code{--skip-new}.

@itemize @bullet

@item

Safer; Even if @code{MySQL} crashes or you get hardware problems, you

Safer; Even if @strong{MySQL} crashes or you get hardware problems, you

can get your data back;  Either by automatic recovery or from a backup

+ the transaction log.

@item

@item

On Linux, you can get much more performance (up to 100 % under load is

not uncommon) by using hdpram to configure your disks interface!  The

following should be quite good hdparm options for @code{MySQL} (and

following should be quite good hdparm options for @strong{MySQL} (and

probably many other applications):

@example

hdparm -m 16 -d 1

... WHERE index_part1=1 OR index_part2=10  /* No index spans all rows */

@end example

Note that in some cases @code{MySQL} will not use an index, even if one

Note that in some cases @strong{MySQL} will not use an index, even if one

would be available.  Some of the cases where this happens are:

@itemize @bullet

If you use @code{LEFT JOIN} to find rows that doesn't exist in some

table and you have the following test: @code{column_name IS NULL} in the

@code{WHERE} part, where column_name is a column that is declared as

@code{NOT NULL}, then @code{MySQL} will stop searching after more rows

@code{NOT NULL}, then @strong{MySQL} will stop searching after more rows

(for a particular key combination) after it has found one row that

matches the @code{LEFT JOIN} condition.

@end itemize

If you do @code{myslqadmin shutdown} on a socket (in other words, on a

the computer where @code{mysqld} is running), @code{mysqladmin} will

wait until the @code{MySQL} @code{pid-file} is removed to ensure that

the @code{mysqld server} has stopped properly.

wait until the @strong{MySQL} @code{pid-file} is removed to ensure that

the @code{mysqld} server has stopped properly.

@node mysqldump, mysqlimport, mysqladmin, Tools

@section Dumping the structure and data from MySQL databases and tables

you are dumping a big database.

Note that if you are using a new copy of the @code{mysqldump} program

and you are going to do a dump that will be read into a very old @code{MySQL}

and you are going to do a dump that will be read into a very old @strong{MySQL}

server, you should not use the @code{--opt} or @code{-e} options.

@code{mysqldump} supports the following options:

likely it is that we can fix the problem!

@node Common programs, Problems, ODBC, Top

@chapter Using @code{MySQL} with some common programs

@chapter Using MySQL with some common programs

@menu

* Apache::                      Using @strong{MySQL} with Apache

into a @strong{MySQL} table. @xref{Contrib}.

You can change the Apache logging format to be easily readable by

@code{MySQL} by putting the following into the Apache configuration file:

@strong{MySQL} by putting the following into the Apache configuration file:

@example

LogFormat \

On Windows you can connect only with TCP/IP if the @code{mysqld} server

is running on Win95/Win98. If it's running on NT, you can also connect

with named pipes.  The name of the named pipe is @code{MySQL}.  If you

with named pipes.  The name of the named pipe is @strong{MySQL}.  If you

don't give a hostname when connecting to @code{mysqld}, a @strong{MySQL} client

will first try to connect to the named pipe and if this doesn't work it

will connect to the TCP/IP port.  You can force the use of named pipes

@item Error: "Fatal error: Call to unsupported or undefined function mysql_connect() in .."

This means that your PHP version isn't compiled with @strong{MySQL} support.

You can either compile a dynamic @strong{MySQL} module and load it into PHP or

recompile PHP with built-in @code{MySQL} support.  This is described in

recompile PHP with built-in @strong{MySQL} support.  This is described in

detail in the PHP manual.

@end itemize

@node Cplusplus, Python, PHP, Clients

@section MySQL C++ APIs

Two API's are available in the @strong{MySQL}

Two APIs are available in the @strong{MySQL}

@uref{http://www.mysql.com/Contrib/,Contrib directory}.

@node Python, Tcl, Cplusplus, Clients

@code{PostgreSQL} has some more advanced features like user-defined

types, triggers, rules and some transaction support (currently it's

has about same symantic as @code{MySQL}'s transactions in that the

has about same symantic as @strong{MySQL}'s transactions in that the

transaction is not 100 % atomic) . However, PostgreSQL lacks

many of the standard types and functions from ANSI SQL and ODBC. See the

@uref{http://www.mysql.com/information/crash-me.php, @code{crash-me} web page}

@uref{http://www.mysql.com/Downloads/Contrib/00-README, 00-README}

This listing.

@appendixsec API's

@appendixsec APIs

@itemize @bullet

@item Perl modules

Added mysqld variable @code{created_tmp_disk_tables}.

@item

To make it possibly to reliable dump and restore tables with

@code{TIMESTAMP(X)} columns, @code{MySQL} now reports columns with X

@code{TIMESTAMP(X)} columns, @strong{MySQL} now reports columns with X

other than 14 or 8 to be strings.

@item

Changed sort order for latin1 as it was before 3.23.22.  Any table with

@appendixsubsec Changes in release 3.23.22

@itemize @bullet

@item

Fixed that @code{lex_hash.h} is created properly for each @code{MySQL}

Fixed that @code{lex_hash.h} is created properly for each @strong{MySQL}

distribution.

@item

Fixed that @code{MASTER} and @code{COLLECTION} are not reserved words.

not all duplicates were removed in queries of the above type.  In

addition, the new code is MUCH faster.

@item

Added patches to make @code{MySQL} compile on MacOS X.

Added patches to make @strong{MySQL} compile on Mac OS X.

@item

Added option @code{IF NOT EXISTS} to @code{CREATE DATABASE}.

@item

numerical column @strong{MySQL} will store 0 into it.

@item

If you try to to store @code{NULL} into a column that doesn't take

@code{NULL} values, @code{MySQL} will store 0 or @code{''} (empty

@code{NULL} values, @strong{MySQL} will store 0 or @code{''} (empty

string) in it instead. (This behavour can however be changed with the

-DDONT_USE_DEFAULT_FIELDS compile option).

@item