Merge bk-internal:/home/bk/mysql-5.1-new

test -z "$INSTALL_SCRIPT" && INSTALL_SCRIPT='${INSTALL_PROGRAM}'

# Not critical since the generated file is distributed

AC_PROG_YACC

AC_CHECK_PROGS(YACC, ['bison -y -p MYSQL'])

AC_CHECK_PROG(PDFMANUAL, pdftex, manual.pdf)

AC_CHECK_PROG(DVIS,      tex,    manual.dvi)

//

View	Create View

v1	CREATE ALGORITHM=UNDEFINED DEFINER=`root`@`localhost` SQL SECURITY DEFINER VIEW `v1` AS select sql_no_cache `test`.`t1`.`id` AS `id` from `t1`

create table t1(f1 int, f2 int);

create view v1 as select ta.f1 as a, tb.f1 as b from t1 ta, t1 tb where ta.f1=tb

.f1 and ta.f2=tb.f2;

insert into t1 values(1,1),(2,2);

create view v2 as select * from v1 where a > 1 with check option;

select * from v2;

a	b

2	2

update v2 set b=3 where a=2;

select * from v2;

a	b

3	3

drop view v2, v1;

drop table t1;

# ----------------------------------------------------------------------------

# $mysql_errno contains the return code of the last command

# send to the server.

# sent to the server.

# ----------------------------------------------------------------------------

# get $mysql_errno before the first statement

#     $mysql_errno should be -1

# ----------------------------------------------------------------------------

# Negative case(statement):

# The dervied table t1 does not contain a column named 'friedrich' . 

# The derived table t1 does not contain a column named 'friedrich' . 

# --> ERROR 42S22: Unknown column 'friedrich' in 'field list and

# --> 1054: Unknown column 'friedrich' in 'field list'

# ----------------------------------------------------------------------------

# The following unmasked unsuccessful statement must give

# 1. mysqltest gives a 'failed'

# 2. does not produce a r/<test case>.reject file !!!

# PLEASE uncomment it and check it's effect

# PLEASE uncomment it and check its effect

#select friedrich from (select 1 as otto) as t1;

# test cases for $mysql_errno

#

# $mysql_errno is a builtin variable of mysqltest and contains the return code

# of the last command send to the server.

# of the last command sent to the server.

#

#      The following test cases often initialize $mysql_errno to 1064 by 

#      a command with wrong syntax.

execute stmt;

eval select $mysql_errno as "after_successful_execute" ;

# failing execute (table dropped)

# failing execute (table has been dropped)

drop table t1;

--error 1064

garbage ;

# ----------------------------------------------------------------------------

# test cases for "--disable_abort_on_error"

#

# "--disable_abort_on_error" switches the abort of mysqltest

# after "unmasked" failing statements off.

# "--disable_abort_on_error" switches off the abort of mysqltest

# after "unmasked" failing statements.

#

# The default is "--enable_abort_on_error".

#

#   --error <error number>  and  --error <error number>

# in the line before the failing statement.

#

# There are some additional test case for $mysql_errno

# There are some additional test cases for $mysql_errno

# because "--disable_abort_on_error" enables a new situation.

# Example: "unmasked" statement fails + analysis of $mysql_errno

# ----------------------------------------------------------------------------

# ----------------------------------------------------------------------------

# Switch the abort on error off and check the effect on $mysql_errno

# Switch off the abort on error and check the effect on $mysql_errno

# ----------------------------------------------------------------------------

--error 1064

garbage ;

# ----------------------------------------------------------------------------

# Test detect end of line "junk"

# Most likely causes by a missing delimiter

# Most likely caused by a missing delimiter

# ----------------------------------------------------------------------------

# Too many parameters to function

--source include/show_msg80.inc

#

# Test --enable_parsning / disable_parsning

# Test --enable_parsing / disable_parsing

#

--disable_query_log

--disable_parsing

#

# Test that mysqltest fails when there are no queries executed

# but a result file exist

# but a result file exists

# NOTE! This will never happen as long as it's not allowed to have

# test files that does not produce any output

# test files that produce no output

#--exec echo "something" > $MYSQLTEST_VARDIR/tmp/result_file.result

#--exec echo "let \$i= 1;" > $MYSQLTEST_VARDIR/tmp/query.sql

#--error 1

drop view v1;

//

delimiter ;//

#

# Bug#17726 Not checked empty list caused endless loop

#

create table t1(f1 int, f2 int);

create view v1 as select ta.f1 as a, tb.f1 as b from t1 ta, t1 tb where ta.f1=tb

.f1 and ta.f2=tb.f2;

insert into t1 values(1,1),(2,2);

create view v2 as select * from v1 where a > 1 with check option;

select * from v2;

update v2 set b=3 where a=2;

select * from v2;

drop view v2, v1;

drop table t1;

  {

    table_map tmp_table_map;

    while (item->type() == Item::COND_ITEM &&

	   ((Item_cond*) item)->functype() == functype())

	   ((Item_cond*) item)->functype() == functype() &&

           !((Item_cond*) item)->list.is_empty())

    {						// Identical function

      li.replace(((Item_cond*) item)->list);

      ((Item_cond*) item)->list.empty();