An error occurred fetching the project authors.
- 08 Oct, 2005 1 commit
-
-
serg@serg.mylan authored
(and contain extern "C" when necessary)
-
- 04 Oct, 2005 1 commit
-
-
jani@ua141d10.elisa.omakaista.fi authored
Some options were declared as 'bool', but since those are being handled in my_getopt.c, bool can be machine dependent. To make sure it works in all circumstances, the type should be my_bool for C (not C++) programs.
-
- 15 Sep, 2005 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 14 Sep, 2005 1 commit
-
-
sasha@asksasha.com authored
present): the problem originally was that the tables in auxilliary_tables did not have the correct real_name, which caused problems in the second call to tables_ok(). The fix corrects the real_name problem, and also sets the updating flag properly, which makes the second call to tables_ok() unnecessary.
-
- 08 Aug, 2005 1 commit
-
-
monty@mysql.com authored
- Fixed some error condtion when handling dates with 'T' - Added extra test for bug #11867 (Wrong result with "... WHERE ROW( a, b ) IN ( SELECT DISTINCT a, b WHERE ...)" to show it's not yet fixed - Safety fixes and cleanups
-
- 30 Jul, 2005 1 commit
-
-
sasha@asksasha.com authored
to connect
-
- 29 Jul, 2005 1 commit
-
-
sasha@asksasha.com authored
-
- 26 Jul, 2005 1 commit
-
-
monty@mysql.com authored
Fixed portability problem with bool in C programs Moved close_thread_tables out from LOCK_thread_count mutex (safety fix) my_sleep() -> pthread_cond_timedwait()
-
- 14 Jul, 2005 2 commits
-
-
konstantin@mysql.com authored
ETIME was returned by cond_timedwait (sic, the pre-POSIX1001b function) on Solaris 2.6 and 2.7. pthread_cond_timedwait on Solaris returns ETIMEDOUT. The standard requirement is that the only additional return value of pthred_cond_timedwait compared to pthread_cond_wait is ETIMEDOUT. Let us not bloat the application code with redundant checks, and if we're ever to work on a platform that returns a non-standard value, we should write a wrapper for that platform (like we do, e.g., for Windows).
-
stewart@mysql.com authored
Only reproducable in 5.1-wl2325, although the missing code is missing from 4.0 and up.
-
- 13 Jul, 2005 1 commit
-
-
lars@mysql.com authored
-
- 12 Jul, 2005 1 commit
-
-
lars@mysql.com authored
-
- 22 Jun, 2005 1 commit
-
-
svoj@mysql.com authored
Fix GCC 4.0 link failure. Better CXX_VERSION guessing.
-
- 19 Jun, 2005 1 commit
-
-
svoj@mysql.com authored
Fix for yaSSL link failures with Forte Developer 7, MIPSpro Compilers, Compaq C++. These compilers have problem with implicit template instantiation in archives (libyassl.a, libtaocrypt.a). Instantiate templates explicitly. Fix for yaSSL link failure on powermacg5 (gcc 3.3). When -O3 is specified gcc inlines __cxa_pure_virtual. This is wrong behavior, __cxa_pure_virtual must never be inlined.
-
- 02 Jun, 2005 1 commit
-
-
brian@zim.(none) authored
Mainly cleanups for gcc 4.0. Some small pieces from looking at -Wall. Removed a number of dumb things in ha_tina.
-
- 05 May, 2005 1 commit
-
-
gbichot@quadita2.mysql.com authored
Approximative fixes for BUG#2610,2611,9100 i.e. WL#2146 binlogging/replication of routines (stored procs and functions). Approximative, because it's using our binlogging way (what we call "query"-level) and this is not as good as record-level binlog (5.1) would be. It imposes several limitations to routines, and has caveats (which I'll document, and for which the server will try to issue errors but that is not always possible). Reason I don't propagate caller info to the binlog as planned is that on master and slave users may be different; even with that some caveats would remain.
-
- 23 Mar, 2005 1 commit
-
-
gbichot@quadita2.mysql.com authored
"After Monty's review" changes to the fix for BUG#8325 "Deadlock in replication thread stops replication": s/sleep/safe_sleep (thread safe); sleep 0/1/2/3/4/5/5/5 (get slave less late); no message on error log (deadlock is too common sometimes), a global counter instead (SHOW STATUS LIKE 'slave_retried_transactions'). Plus a fix for libmysql/Makefile.shared
-
- 22 Mar, 2005 1 commit
-
-
gbichot@production.mysql.com authored
fails there; until we find reason (me and possibly Konstantin).
-
- 21 Mar, 2005 1 commit
-
-
gbichot@production.mysql.com authored
of SET ONE_SHOT; storing tz info directly in event (if this info is needed), it's now allowed to have different global tz on master and slave.
-
- 09 Mar, 2005 1 commit
-
-
serg@serg.mylan authored
-
- 02 Mar, 2005 2 commits
-
-
guilhem@mysql.com authored
First part of fix for BUG#7998 "Replication should be more clever about when to replicate RELEASE_LOCK()" (next part is updating test results)
-
guilhem@mysql.com authored
in slave SQL thread: if a transaction fails because of InnoDB deadlock or innodb_lock_wait_timeout exceeded, optionally retry the transaction a certain number of times (new variable --slave_transaction_retries).
-
- 25 Feb, 2005 1 commit
-
-
monty@mysql.com authored
(Found during build process)
-
- 17 Feb, 2005 1 commit
-
-
serg@serg.mylan authored
-
- 09 Feb, 2005 1 commit
-
-
serg@serg.mylan authored
auto-commit on Xid_log_event
-
- 07 Feb, 2005 1 commit
-
-
acurtis@pcgem.rdg.cyberkinetica.com authored
-
- 03 Feb, 2005 1 commit
-
-
guilhem@mysql.com authored
we store 7 bytes (1 + 2*3) in every Query_log_event. In the future if users want binlog optimized for small size and less safe, we could add --binlog-no-charset (and binlog-no-sql-mode etc): charset info is something by design optional (even if for now we don't offer possibility to disable it): it's not a binlog format change. We try to reduce the number of get_charset() calls in the slave SQL thread to a minimum by caching the charset read from the previous event (which will often be equal to the one of the current event). We don't use SET ONE_SHOT for charset-aware repl (we still do for timezones, will be fixed later). No more errors if one changes the global value of charset vars on master or slave (as we log charset info in all Query_log_event). Not fixing Load_log_event as it will be rewritten soon by Dmitri. Testing how mysqlbinlog behaves in rpl_charset.test. mysqlbinlog needs to know where charset file is (to be able to convert a charset number found in binlog (e.g. in User_var_log_event) to a charset name); mysql-test-run needs to pass the correct value for this option to mysqlbinlog. Many result udpates (adding charset info into every event shifts log_pos in SHOW BINLOG EVENTS). Roughly the same job is to be done for timezones :)
-
- 01 Feb, 2005 1 commit
-
-
serg@serg.mylan authored
-
- 24 Jan, 2005 1 commit
-
-
serg@serg.mylan authored
-
- 18 Jan, 2005 1 commit
-
-
guilhem@mysql.com authored
5.0 has a different way of knowing if master is < 3.23.57
-
- 17 Jan, 2005 1 commit
-
-
guilhem@mysql.com authored
Working around hang of master < 3.23.50 on SELECT @@unknown_var (to enable 3.23.49->4.1.10 replication)
-
- 06 Jan, 2005 1 commit
-
-
monty@mysql.com authored
Split TABLE to TABLE and TABLE_SHARE (TABLE_SHARE is still allocated as part of table, will be fixed soon) Created Field::make_field() and made Field_num::make_field() to call this Added 'TABLE_SHARE->db' that points to database name; Changed all usage of table_cache_key as database name to use this instead Changed field->table_name to point to pointer to alias. This allows us to change alias for a table by just updating one pointer. Renamed TABLE_SHARE->real_name to table_name Renamed TABLE->table_name to alias Renamed TABLE_LIST->real_name to table_name
-
- 16 Dec, 2004 2 commits
-
-
guilhem@mysql.com authored
-
guilhem@mysql.com authored
because old behaviour was somewhat nonsensical (kind of bug). Changes are that if repl threads are down or disconnected the column will be NULL, and if master is idle the column will not grow indefinitely anymore.
-
- 09 Dec, 2004 1 commit
-
-
guilhem@mysql.com authored
All our programs which use mysql_real_connect() and mysql_connect() are updated accordingly, though I have deliberately made mysqlimport not reconnect anymore (already true for mysqldump >= 4.1.8). All Connector devs have been warned about the change I'm doing here - which was agreed with Monty, and fixes BUG#2555.
-
- 03 Dec, 2004 1 commit
-
-
lars@mysql.com authored
1 if the return type is int or int_fast8_t. The test case that showed this problem is rpl000001 and the tested version was MySQL 5.0.2. The compiler with the problem is GCC 3.0.4 runing on "Linux bitch 2.4.18 #2 Thu Apr 11 14:37:17 EDT 2002 sparc64 unknown". By changing the return type to bool the problem disappear. (Another way to make the problem disappear is to simply print the returned value with printf("%d",?). The printed returned value is always 0 in the test cases I have run.) This is only a partial solution to the problem, since someone could later change the return type of the function back to int or some other type that does not work.
-
- 26 Nov, 2004 1 commit
-
-
monty@mysql.com authored
(Cleanups and better bug fixes)
-
- 25 Nov, 2004 1 commit
-
-
mats@mysql.com authored
slave SQL thread is started.
-
- 17 Nov, 2004 1 commit
-
-
guilhem@mysql.com authored
Moving the part of user_var.test using UCS2 to ctype_ucs.test
-
- 13 Nov, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
used only one implementation of format parser of (printf) fixed multistatement
-