Custom Query (196 matches)

MySQL supports ​two major replication formats: statement-based, where the query is logged and replayed, and row-based, where the changed data is logged and replayed. Statement-based is much older and presumed more stable, and the default in 5.x; ​row-based handles a couple of nondeterministic queries that statement-based replication can't. MySQL 5.1.8 also introduced ​mixed-format logging, which uses statement-based replication where it can and row-based where necessary. 5.1.12 made mixed replication the default, until it was ​reverted in 5.1.29 on the grounds that 5.1 should be compatible with 5.0. We should decide on our own whether we want to use mixed replication (I think there's no compelling need to switch to row-based replication for everything). Among other obvious benefits, more reliable replication means that backups are more likely to match what you see on the primary.

Relatedly, MySQL used to permit users to set a session variable, ​`binlog_format`, to switch logging types for the duration of that session. However, this ability was ​restricted to users with the SUPER privilege (which has always been required for setting that as a _global_ variable), because someone claimed that DBAs might write code that required row-based replication and didn't want a mere user to be able to switch to statement-based replication and foil the DBA's plans. While I question the validity of such a possibility, we certainly don't have DBAs, so it might be worth locally reverting that patch so that users and applications have the option of switching to row-based replication if they prefer it. This would be especially important if we go through autoinstalled apps to see what, if anything, wouldn't work properly statement-based replication.

Once we resolve #157, it would be cute if we can get guest console output (perhaps starting once the guests have booted up and presented a logini prompt) to get sent to zephyr, so we see things like oopses and OOM kills and panics and other stuff that's indicative of a problem but unlikely to get logged from within the host and successfully reach zephyr that way.

I clicked on "Fedora 11" on the milestones page and got:

Trac detected an internal error:

ProgrammingError?: (1064, "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'sensitive\nFROM ticket AS t\n LEFT OUTER JOIN ticket_custom AS sensitive ON (id=s' at line 1")

File "/usr/lib/python2.6/site-packages/trac/web/main.py", line 450, in _dispatch_request
  dispatcher.dispatch(req)
File "/usr/lib/python2.6/site-packages/trac/web/main.py", line 206, in dispatch
  resp = chosen_handler.process_request(req)
File "/usr/lib/python2.6/site-packages/trac/ticket/query.py", line 836, in process_request
  return self.display_html(req, query)
File "/usr/lib/python2.6/site-packages/trac/ticket/query.py", line 889, in display_html
  tickets = query.execute(req, db)
File "/usr/lib/python2.6/site-packages/trac/ticket/query.py", line 264, in execute
  self.num_items = self._count(sql, args, db)
File "/usr/lib/python2.6/site-packages/trac/ticket/query.py", line 249, in _count
  cursor.execute(count_sql, args);
File "/usr/lib/python2.6/site-packages/trac/db/util.py", line 64, in execute
  return self.cursor.execute(sql_escape_percent(sql), args)
File "/usr/lib64/python2.6/site-packages/MySQLdb/cursors.py", line 173, in execute
  self.errorhandler(self, exc, value)
File "/usr/lib64/python2.6/site-packages/MySQLdb/connections.py", line 36, in defaulterrorhandler
  raise errorclass, errorvalue