Below is the list of changes that have just been committed into a local
5.0 repository of tnurnberg. When tnurnberg does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://dev.mysql.com/doc/mysql/en/installing-source-tree.html
ChangeSet
1.2199 06/06/26 19:44:27 tnurnberg@stripped +1 -0
Merge bk-internal.mysql.com:/home/bk/mysql-5.0-maint
into mysql.com:/home/tnurnberg/review/mysql-5.0-maint-20588
mysql-test/t/mysqldump.test
1.93 06/06/26 19:44:19 tnurnberg@stripped +0 -0
Auto merged
# This is a BitKeeper patch. What follows are the unified diffs for the
# set of deltas contained in the patch. The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User: tnurnberg
# Host: salvation.intern.azundris.com
# Root: /home/tnurnberg/review/mysql-5.0-maint-20588/RESYNC
--- 1.92/mysql-test/t/mysqldump.test 2006-06-23 00:32:36 +02:00
+++ 1.93/mysql-test/t/mysqldump.test 2006-06-26 19:44:19 +02:00
@@ -1146,6 +1146,27 @@
#
+# Bug#18462 mysqldump does not dump view structures correctly
+#
+#
+create table t (qty int, price int);
+insert into t values(3, 50);
+insert into t values(5, 51);
+create view v1 as select qty, price, qty*price as value from t;
+create view v2 as select qty from v1;
+--echo mysqldump {
+--exec $MYSQL_DUMP --compact -F --tab . test
+--exec cat v1.sql
+--echo } mysqldump {
+--exec cat v2.sql
+--echo } mysqldump
+--rm v.sql t.sql t.txt
+drop view v1;
+drop view v2;
+drop table t;
+
+
+#
# Bug#14857 Reading dump files with single statement stored routines fails.
# fixed by patch for bug#16878
#
| Thread |
|---|
| • bk commit into 5.0 tree (tnurnberg:1.2199) | Tatjana A Nuernberg | 26 Jun |