9,587 reputation
11025
bio website
location Cincinnati, OH
age 43
visits member for 2 years, 2 months
seen 4 hours ago

If you question or otherwise fail to recognize the superiority of the relational model... you're doing it wrong.


Oct
6
comment Log all table updates for all tables in MySQL
Have you considered the binary log as a source?
Oct
6
comment MySQL - Checksum won't match between master and slave hosts despite dumping and reloading the table
Granted, the other question does not have a satisfactory answer at all, since the change that occurred between 4.1 and 5.0 should not be impacting you, now... but the question is still the same. I've long-suspected a latent bug in the way CHECKSUM TABLE works. One thing that might be worth trying is doing an OPTIMIZE TABLE on the master to check and see if the checksum remains the same there after the table is rebuilt.
Oct
6
reviewed Close MySQL configuration to connect to multiple local applications
Oct
6
revised Is it possible to modify an existing trigger definition in MySQL?
clarify the question; clearly triggers can be changed with drop/create, but this appears to be asking for an alternative
Oct
6
answered Is it possible to modify an existing trigger definition in MySQL?
Oct
5
comment How to handle too many instances of multiple tables?
Are these tables MyISAM? Are you experiencing a performance issue, now? Are you seeing errors?
Oct
4
answered How to swap roles of Master-Master?
Oct
1
answered Clarification on MySQL Workbench Options File Configuring
Oct
1
comment MySQL 5.6: explicit_defaults_for_timestamp
You need to compare the table definitions among the servers with SHOW CREATE TABLE and then also SELECT @@SQL_MODE;. When replicating from 5.5 to 5.6, cascaded or not, setting explicit_defaults_for_timestamp to 1 was probably the wrong choice, and your table definitions may be different, on at least one of the replicas, since the way CREATE TABLE statements are interpreted is what that variable modifies. Please update the question with what you find.
Sep
30
awarded  Explainer
Sep
29
comment MySQL dies when trying to access a specific database
"Lost connection to MySQL Server..." followed by can't connect message ending in (111) almost certainly means that whatever is happening is actually crashing the server (typically, it will recover and become available on its own, depending on the nature of the crash). Please check the MySQL server's error log and update your question based on what you find there.
Sep
27
reviewed Close Why does mysql give different result for this summations?
Sep
27
reviewed Leave Open Storing a Shipping Address Best Practice
Sep
24
awarded  Autobiographer
Sep
23
answered Dynamic my sql error
Sep
18
comment MySQL - Database has huge overhead but tables don't
What process did you use to recreate the tables?
Sep
18
comment What happens if the mysql database's innodb log files are lost?
@Rafael if the server was stopped gracefully with innodb_fast_shutdown set to 0, and apparently 1, the data in the logs should have already been committed to ibdata1 file and *.ibd files, so there should be no data loss.
Sep
16
answered Replicated timestamp column in different timezone
Sep
16
answered Create t2 instance and connect via Wokrbench
Sep
15
awarded  Yearling