mirror/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-01-30 18:41:56 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
30202 commits 2789 branches 343 tags 1.7 GiB
Commit graph

30202 commits

This branch
This branch
All branches
Author SHA1 Message Date
msvensson@neptunus.(none)
4c866961ed Bug#18474 Unlistable directories yield no info from information_schema, part2 
- Move "chmod" part of information_schema test to separate file
 2006-05-04 17:47:25 +02:00
msvensson@neptunus.(none)
8f7a52ce6c Move "check_running_as_root" to after var directory has been created 2006-05-04 17:44:09 +02:00
jani@ua141d10.elisa.omakaista.fi
0410832526 Merge ua141d10.elisa.omakaista.fi:/home/my/bk/mysql-4.1 
into  ua141d10.elisa.omakaista.fi:/home/my/bk/mysql-5.0
 2006-05-04 18:35:58 +03:00
jani@a193-229-222-105.elisa-laajakaista.fi
3f1019455b Merge jamppa@bk-internal.mysql.com:/home/bk/mysql-4.1 
into  a193-229-222-105.elisa-laajakaista.fi:/home/my/bk/mysql-4.1
 2006-05-04 17:41:07 +03:00
kroki@mysql.com
98949e7a66 Merge mysql.com:/home/tomash/src/mysql_ab/mysql-4.1 
into  mysql.com:/home/tomash/src/mysql_ab/mysql-4.1-bug16372
 2006-05-04 18:36:53 +04:00
kroki@mysql.com
1139d37545 Merge mysql.com:/home/tomash/src/mysql_ab/mysql-4.1 
into  mysql.com:/home/tomash/src/mysql_ab/mysql-4.1-bug16501
 2006-05-04 18:36:00 +04:00
monty@mysql.com
e71ad86cc1 Merge monty@192.168.0.9:/my/mysql-5.0 
into  mysql.com:/home/my/mysql-5.0
 2006-05-04 17:19:43 +03:00
monty@mysql.com
3f2e2664a9 Merge bk-internal.mysql.com:/home/bk/mysql-5.0 
into  mysql.com:/home/my/mysql-5.0
 2006-05-04 17:12:47 +03:00
monty@mysql.com
c33b326d86 Fixed an (unlikely) memory leak 2006-05-04 17:11:40 +03:00
monty@mysql.com
770f03ef02 Merge bk-internal.mysql.com:/home/bk/mysql-5.0 
into  mysql.com:/home/my/mysql-5.0
 2006-05-04 17:08:42 +03:00
jani@ua141d10.elisa.omakaista.fi
634afcc9f8 Merge jamppa@bk-internal.mysql.com:/home/bk/mysql-5.0 
into  ua141d10.elisa.omakaista.fi:/home/my/bk/mysql-5.0
 2006-05-04 17:07:04 +03:00
jani@ua141d10.elisa.omakaista.fi
3e1e98876a Added test case for Bug#18712: Truncation problem. The test 
is only to make sure that this will not be fixed, as it is
intended behaviour. Documentation will be improved accordingly.
 2006-05-04 17:05:21 +03:00
kroki@mysql.com
018d9e17b9 Merge mysql.com:/home/tomash/src/mysql_ab/mysql-4.1 
into  mysql.com:/home/tomash/src/mysql_ab/mysql-4.1-bug16372
 2006-05-04 17:49:21 +04:00
monty@mysql.com
1809adee63 Merge bk-internal.mysql.com:/home/bk/mysql-5.0 
into  mysql.com:/home/my/mysql-5.0
 2006-05-04 15:32:25 +03:00
monty@mysql.com
837ba4f399 Fixed memory leak in sql_parse.cc (lex_end() was not called) 
This caused sp-vars.test to fail
 2006-05-04 15:30:38 +03:00
igor@rurik.mysql.com
da7108d40b Merge rurik.mysql.com:/home/igor/mysql-5.0 
into  rurik.mysql.com:/home/igor/dev/mysql-5.0-0
 2006-05-04 04:55:32 -07:00
svoj@april.(none)
dee1baaefd Fixed heap_btree test failure on 64-bit boxes. 2006-05-04 15:52:09 +05:00
jani@hundin.mysql.fi
d3467c0b4c Merge jamppa@bk-internal.mysql.com:/home/bk/mysql-4.1 
into  hundin.mysql.fi:/home/jani/mysql-4.1
 2006-05-04 13:17:16 +03:00
msvensson@neptunus.(none)
697069af2c Fix warnings 2006-05-04 10:30:08 +02:00
msvensson@neptunus.(none)
15babe1495 Put the "test_running_as_root.txt" file in the vardir to avoid that two mysql-test-run's running in parallel uses the same file 2006-05-04 10:28:49 +02:00
kroki@mysql.com
be84d12320 Merge bk-internal.mysql.com:/home/bk/mysql-5.0 
into  mysql.com:/home/tomash/src/mysql_ab/mysql-5.0-real
 2006-05-04 11:31:07 +04:00
kroki@mysql.com
74fd0beefa Merge mysql.com:/home/tomash/src/mysql_ab/mysql-4.1 
into  mysql.com:/home/tomash/src/mysql_ab/mysql-4.1-bug16501
 2006-05-04 11:25:48 +04:00
tnurnberg@mysql.com
a5f440f891 Merge tnurnberg@bk-internal.mysql.com:/home/bk/mysql-4.1 
into  mysql.com:/home/mysql-4.1-19025e
 2006-05-04 09:06:27 +02:00
holyfoot@mysql.com
d5c6f594de Merge abotchkov@bk-internal.mysql.com:/home/bk/mysql-5.0 
into mysql.com:/home/hf/work/mysql-5.0.mrg
 2006-05-04 10:13:34 +05:00
holyfoot@mysql.com
540481aef9 Merge mysql.com:/home/hf/work/mysql-4.1.mrg 
into mysql.com:/home/hf/work/mysql-5.0.mrg
 2006-05-04 09:59:32 +05:00
holyfoot@deer.(none)
2f154ab410 test result fixed 2006-05-04 09:58:03 +05:00
igor@rurik.mysql.com
dd839667c7 Post-review changes. 2006-05-03 21:35:27 -07:00
igor@rurik.mysql.com
3dc06cb3fa Merge rurik.mysql.com:/home/igor/mysql-5.0 
into  rurik.mysql.com:/home/igor/dev/mysql-5.0-0
 2006-05-03 19:38:37 -07:00
tnurnberg@mysql.com
5becb110e0 Bug#19025 4.1 mysqldump doesn't correctly dump "auto_increment = [int]" 
mysqldump / SHOW CREATE TABLE will show the NEXT available value for
the PK, rather than the *first* one that was available (that named in
the original CREATE TABLE ... AUTO_INCREMENT = ... statement).

This should produce correct and robust behaviour for the obvious use
cases -- when no data were inserted, then we'll produce a statement
featuring the same value the original CREATE TABLE had; if we dump
with values, INSERTing the values on the target machine should set the
correct next_ID anyway (and if not, we'll still have our AUTO_INCREMENT =
... to do that). Lastly, just the CREATE statement (with no data) for
a table that saw inserts would still result in a table that new values
could safely be inserted to).

There seems to be no robust way however to see whether the next_ID
field is > 1 because it was set to something else with CREATE TABLE
... AUTO_INCREMENT = ..., or because there is an AUTO_INCREMENT column
in  the table (but no initial value was set with AUTO_INCREMENT = ...)
and then one or more rows were INSERTed, counting up next_ID. This
means that in both cases, we'll generate an AUTO_INCREMENT =
... clause in SHOW CREATE TABLE / mysqldump.  As we also show info on,
say, charsets even if the user did not explicitly give that info in
their own CREATE TABLE, this shouldn't be an issue.

As per above, the next_ID will be affected by any INSERTs that have
taken place, though.  This /should/ result in correct and robust
behaviour, but it may look non-intuitive to some users if they CREATE
TABLE ... AUTO_INCREMENT = 1000 and later (after some INSERTs) have
SHOW CREATE TABLE give them a different value (say, CREATE TABLE
... AUTO_INCREMENT = 1006), so the docs should possibly feature a
caveat to that effect.

It's not very intuitive the way it works now (with the fix), but it's
*correct*.  We're not storing the original value anyway, if we wanted
that, we'd have to change on-disk representation?

If we do dump/load cycles with empty DBs, nothing will change.  This
changeset includes an additional test case that proves that tables
with rows will create the same next_ID for AUTO_INCREMENT = ... across
dump/restore cycles.

Confirmed by support as likely solution for client's problem.
 2006-05-04 03:12:51 +02:00
svojtovich@production.mysql.com
1890b04e13 Merge svojtovich@bk-internal.mysql.com:/home/bk/mysql-5.0 
into  production.mysql.com:/usersnfs/svojtovich/mysql-5.0
 2006-05-03 23:17:17 +02:00
holyfoot@mysql.com
2f7ac18f22 Merge bk@192.168.21.1:mysql-5.0 
into mysql.com:/home/hf/work/mysql-5.0.mrg
 2006-05-04 02:17:17 +05:00
pekka@mysql.com
ec42119233 Merge pnousiainen@bk-internal.mysql.com:/home/bk/mysql-4.1 
into  mysql.com:/space/pekka/ndb/version/my50
 2006-05-03 23:17:16 +02:00
aivanov@mysql.com
7a74734219 Merge aivanov@bk-internal.mysql.com:/home/bk/mysql-5.0 
into  mysql.com:/home/alexi/innodb/mysql-5.0-ss521
 2006-05-04 01:17:15 +04:00
aivanov@mysql.com
4cff042a58 Applied innodb-5.0-ss521 snapshot. 
Fixed BUG#19366: "consistent_snapshot.test fails".
 2006-05-04 00:32:34 +04:00
holyfoot@mysql.com
7d47127e86 Merge bk@192.168.21.1:mysql-4.1 
into mysql.com:/home/hf/work/mysql-4.1.mrg
 2006-05-04 00:45:56 +05:00
aivanov@mysql.com
b695bb4624 Merge aivanov@bk-internal.mysql.com:/home/bk/mysql-4.1 
into  mysql.com:/home/alexi/innodb/mysql-4.1-ss26
 2006-05-03 23:45:55 +04:00
aivanov@mysql.com
a7122276a4 Merge mysql.com:/home/alexi/innodb/mysql-4.1-ss26-work 
into  mysql.com:/home/alexi/innodb/mysql-5.0-ss521-work
 Null-merge.
 2006-05-03 23:29:27 +04:00
aivanov@mysql.com
d546f0d93e Applied innodb-4.1-ss26 snapshot. 
Fixed BUG#19366: "consistent_snapshot.test fails".
 2006-05-03 23:25:01 +04:00
holyfoot@mysql.com
e5a22d1bca Merge bk@192.168.21.1:mysql-4.1 
into mysql.com:/home/hf/work/mysql-4.1.mrg
 2006-05-04 00:03:58 +05:00
msvensson@neptunus.(none)
667435103d Check if "../libtool" is available and use it only when it is. 2006-05-03 20:04:57 +02:00
msvensson@neptunus.(none)
5feae9aa4e Merge bk-internal:/home/bk/mysql-5.0-maint 
into  neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint
 2006-05-03 19:41:57 +02:00
msvensson@neptunus.(none)
7aba56f452 Use "const char*" for variable found, forte complains "Cannot use const char* to initialize char*" otherwise 2006-05-03 17:55:30 +02:00
msvensson@neptunus.(none)
896704c648 Remove C++ comments 
Formatting
 2006-05-03 16:59:02 +02:00
holyfoot@deer.(none)
5b5db01a46 merging fix 2006-05-03 19:01:29 +05:00
msvensson@neptunus.(none)
7c8c14c435 Move "max-connect-retries" option to get alpabetichal order 2006-05-03 15:53:59 +02:00
holyfoot@deer.(none)
81e625ac4a merging fix 2006-05-03 17:43:32 +05:00
msvensson@devsrv-b.mysql.com
4a755e085b Merge msvensson@msvensson.mysql.internal:/home/msvensson/mysql/mysql-5.0-maint 
into  devsrv-b.mysql.com:/users/msvensson/mysql-5.0-maint
 2006-05-03 14:12:38 +02:00
msvensson@neptunus.(none)
f0ac0fdf06 Add an untrusted cacert used when testing 2006-05-03 14:10:22 +02:00
msvensson@neptunus.(none)
e1b41812b7 Load CA certs before setting local certs. 
Make it possible to get the yaSSL error message printed in the DBUG log file.
 2006-05-03 14:09:08 +02:00
msvensson@neptunus.(none)
99475e7f4c Add tests for connecting to server with invalid and blank certs. 2006-05-03 14:06:34 +02:00