An error occurred fetching the project authors.
- 15 Nov, 2006 2 commits
-
-
msvensson@neptunus.(none) authored
Fix merge errors
-
msvensson@neptunus.(none) authored
-
- 18 Oct, 2006 2 commits
-
-
iggy@rolltop.ignatz42.dyndns.org authored
-
iggy@rolltop.ignatz42.dyndns.org authored
The mysqldump command with both the --xml and --hex-blob options will output blob data encoded as hexBinary. The proper XML datatype is xs:hexBinary. The correct XML datatype is specified be setting the xsi_type attribute equal to xs:hexBinary for each encoded element.
-
- 21 Sep, 2006 1 commit
-
-
- 20 Sep, 2006 1 commit
-
-
- 18 Sep, 2006 1 commit
-
-
mats@romeo.(none) authored
-
- 15 Sep, 2006 1 commit
-
-
- 14 Sep, 2006 1 commit
-
-
iggy@rolltop.ignatz42.dyndns.org authored
Bug#21424 mysqldump failing to export/import views. Dumps are created for the tables in each specified database then for the views in each specified database. This bug occurs when any database's views depend on the mysql database's table data while being restored. Added command line option --flush-privileges to the mysqldump utility which causes a FLUSH PRIVILIGES statement to be written to the dump after the mysql database.
-
- 01 Sep, 2006 2 commits
-
-
jimw@rama.(none) authored
-
jimw@rama.(none) authored
so that 4.1 and 5.0 tests are all in the right place and no tests are duplicated.
-
- 29 Aug, 2006 1 commit
-
-
iggy@rolltop.ignatz42.dyndns.org authored
-
- 28 Aug, 2006 1 commit
-
-
iggy@rolltop.ignatz42.dyndns.org authored
init_dumping now accepts a function pointer to the table or view specific init_dumping function. This allows both tables and views to use the init_dumping function.
-
- 17 Aug, 2006 1 commit
-
-
jimw@rama.(none) authored
The problem was that the error handling was using a too-small buffer to print the error message generated. We fix this by not using a buffer at all, but by using fprintf() directly. There were also some problems with the error handling in table dumping that was exposed by this fix that were also corrected.
-
- 14 Aug, 2006 3 commits
-
-
brian@zim.(none) authored
-
kostja@bodhi.local authored
-
kostja@bodhi.local authored
-
- 10 Aug, 2006 1 commit
-
-
andrey@example.com authored
-
- 03 Aug, 2006 3 commits
-
-
tsmith@maint1.mysql.com authored
-
msvensson@neptunus.(none) authored
-
msvensson@neptunus.(none) authored
-
- 02 Aug, 2006 1 commit
-
-
grog@eucla.lemis.com authored
Quote PKEY.
-
- 29 Jul, 2006 1 commit
-
-
jimw@rama.(none) authored
-
- 27 Jul, 2006 1 commit
-
-
anozdrin/alik@booka. authored
Fix for BUG#16676: Database CHARSET not used for stored procedures The problem in BUG#16211 is that CHARSET-clause of the return type for stored functions is just ignored. The problem in BUG#16676 is that if character set is not explicitly specified for sp-variable, the server character set is used instead of the database one. The fix has two parts: - always store CHARSET-clause of the return type along with the type definition in mysql.proc.returns column. "Always" means that CHARSET-clause is appended even if it has not been explicitly specified in CREATE FUNCTION statement (this affects BUG#16211 only). Storing CHARSET-clause if it is not specified is essential to avoid changing character set if the database character set is altered in the future. NOTE: this change is not backward compatible with the previous releases. - use database default character set if CHARSET-clause is not explicitly specified (this affects both BUG#16211 and BUG#16676). NOTE: this also breaks backward compatibility.
-
- 24 Jul, 2006 1 commit
-
-
msvensson@neptunus.(none) authored
- Add call to 'safe_exit' function when db query fails.
-
- 19 Jul, 2006 1 commit
-
-
- 17 Jul, 2006 1 commit
-
-
iggy@rolltop.ignatz42.dyndns.org authored
-
- 14 Jul, 2006 3 commits
-
-
-
-
mysqldump did not select the correct database before trying to dump views from it. this resulted in an empty result set, which in turn startled mysql-dump into a core-dump. this only happened for views, not for tables, and was only visible with multiple databases that weren't by sheer luck in the order mysqldump required, anyway. this fixes by selecting the correct database before dumping views; it also catches the empty set-condition if it should occur for other reasons.
-
- 13 Jul, 2006 1 commit
-
-
mysqldump did not select the correct database before trying to dump views from it. this resulted in an empty result set, which in turn startled mysql-dump into a core-dump. this only happened for views, not for tables, and was only visible with multiple databases that weren't by sheer luck in the order mysqldump required, anyway. this fixes by selecting the correct database before dumping views; it also catches the empty set-condition if it should occur for other reasons.
-
- 03 Jul, 2006 1 commit
-
-
cmiller@zippy.(none) authored
where it isn't. Removed a test where the merge was incorrect (and a test duplicated.)
-
- 21 Jun, 2006 2 commits
-
-
lars@mysql.com authored
-
igreenhoe@mysql.com authored
-
- 19 Jun, 2006 1 commit
-
-
lars@mysql.com authored
-
- 15 Jun, 2006 1 commit
-
-
lars@mysql.com authored
-
- 31 May, 2006 2 commits
-
-
jani@ua141d10.elisa.omakaista.fi authored
-
tnurnberg@mysql.com authored
(The above problem only occurs with -T -- create a separate file for each table / view.) This ChangeSet results in correct output of view- information while omitting the information for the view's stand-in table. The rationale is that with -T, the user is likely interested in transferring part of a database, not the db in its entirety (that would be difficult as replay order is obscure, the files being named for the table/view they contain rather than getting a sequence number).
-
- 30 May, 2006 1 commit
-
-
tnurnberg@mysql.com authored
'show create' works even on views that are short of a base-table (this throw a warning though, like you would expect). Unfortunately, this is not what mysqldump uses; it creates stand-in tables and hence requests 'show fields' on the view which fails with missing base-tables. The --force option prevents the dump from stopping at this point; furthermore this patch dumps a comment showing create for the offending view for better diagnostics. This solution was confirmed by submitter as solving their/clients' problem. Problem might become non-issue once mysqldump no longer creates stand-in tables.
-
- 29 May, 2006 1 commit
-
-
msvensson@neptunus.(none) authored
-