- 10 Aug, 2006 1 commit
-
-
pgalbraith/patg@govinda.patg.net authored
-
- 07 Aug, 2006 2 commits
-
-
svoj@may.pils.ru authored
-
svoj@may.pils.ru authored
into may.pils.ru:/home/svoj/devel/mysql/BUG14770/mysql-5.0-engines
-
- 02 Aug, 2006 1 commit
-
-
svoj@may.pils.ru authored
columns Fixed confusing warning. Quoting INSERT section of the manual: ---- Inserting NULL into a column that has been declared NOT NULL. For multiple-row INSERT statements or INSERT INTO ... SELECT statements, the column is set to the implicit default value for the column data type. This is 0 for numeric types, the empty string ('') for string types, and the "zero" value for date and time types. INSERT INTO ... SELECT statements are handled the same way as multiple-row inserts because the server does not examine the result set from the SELECT to see whether it returns a single row. (For a single-row INSERT, no warning occurs when NULL is inserted into a NOT NULL column. Instead, the statement fails with an error.) ---- This is also true for LOAD DATA INFILE. For INSERT user can specify DEFAULT keyword as a value to set column default. There is no similiar feature available for LOAD DATA INFILE.
-
- 01 Aug, 2006 1 commit
-
-
"Test case 'csv' produces incorrect result on OpenBSD" mmapped pages were not being invalidated when writes occurred to the file vi a fd i/o operation. Force explicit invalidation and not rely on implicit invalidation.
-
- 30 Jul, 2006 3 commits
-
-
ingo/mydev@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-bug20719
-
ingo/mydev@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-bug20719
-
ingo/mydev@chilla.local authored
After merge fix
-
- 29 Jul, 2006 2 commits
-
-
ingo/mydev@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-bug20719
-
ingo/mydev@chilla.local authored
After merge fix
-
- 26 Jul, 2006 2 commits
-
-
ingo/mydev@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-bug20719
-
ingo/mydev@chilla.local authored
into chilla.local:/home/mydev/mysql-4.1-bug20719
-
- 25 Jul, 2006 1 commit
-
-
Added HA_NULL_IN_KEY to table flags to allow for nullable unique indexes and added test to verify ha_federated.h: BUG #15133 "unique index with nullable value not accepted in federated table" added HA_NULL_IN_KEY to table flags to allow for nullable unique indexes federated.test: BUG #15133 "unique index with nullable value not accepted in federated table" New test to show that nullable unique indexes work federated.result: BUG #15133 "unique index with nullable value not accepted in federated table" New results for new test
-
- 21 Jul, 2006 3 commits
-
-
ingo/mydev@chilla.local authored
into chilla.local:/home/mydev/mysql-4.1
-
ingo/mydev@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0
-
ingo/mydev@chilla.local authored
Fixed a possible problem with reading of dynamic records when a write cache is active. The cache must be flushed whenever a part of the file in the write cache is to be read. Added a read optimization to _mi_read_dynamic_record(). No test case. This was a hypothetical but existing problem.
-
- 19 Jul, 2006 2 commits
-
-
patg@govinda.patg.net authored
Post merge changes.
-
patg@govinda.patg.net authored
into govinda.patg.net:/home/patg/mysql-build/mysql-5.0-bug18764.2
-
- 18 Jul, 2006 1 commit
-
-
jimw@rama.(none) authored
into rama.(none):/home/jimw/my/mysql-5.0-17608
-
- 17 Jul, 2006 1 commit
-
-
patg@govinda.patg.net authored
Removed logic in ha_federated::write_row, which checks field query ids in the loop which builds the query to run on the remote server.
-
- 12 Jul, 2006 5 commits
-
-
jimw@rama.(none) authored
The Federated storage engine used Field methods that had arbitrary limits on the amount of data they could process, which caused problems with data over that limit (4K). By removing those Field methods and just using features of the String class, we can avoid this problem.
-
kostja@bodhi.local authored
-
mkindahl@dl145k.mysql.com authored
into dl145k.mysql.com:/data0/mkindahl/bk/mysql-5.0-rpl
-
jimw@rama.(none) authored
into rama.(none):/home/jimw/my/mysql-5.0-17766
-
jimw@rama.(none) authored
Changed the error reporting (and a crash) when inserting data into a MERGE table that has no underlying tables or no INSERT_METHOD specified by reporting that it is read-only.
-
- 11 Jul, 2006 6 commits
-
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.0-runtime-merge-41
-
ingo/mydev@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-amerge
-
joerg@trift2. authored
-
joerg@trift2. authored
into trift2.:/M50/mysql-5.0
-
mkindahl@dl145k.mysql.com authored
into dl145k.mysql.com:/data0/mkindahl/bk/MERGE/mysql-5.0-merge
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.0-runtime-merge-41
-
- 10 Jul, 2006 9 commits
-
-
kostja@bodhi.local authored
-
joerg@trift2. authored
into trift2.:/M50/mysql-5.0
-
joerg@trift2. authored
-
kostja@bodhi.local authored
-
ingo/mydev@chilla.local authored
-
guilhem@gbichot3.local authored
into gbichot3.local:/home/mysql_src/mysql-5.0
-
kostja@bodhi.local authored
-
pekka@orca.ndb.mysql.com authored
into orca.ndb.mysql.com:/space_old/pekka/ndb/version/my50-1.2167.1.2
-
pekka@orca.ndb.mysql.com authored
-