maria-developers team mailing list archive

[worklog-noreply@xxxxxxxxxxxx]

-----------------------------------------------------------------------
                              WORKLOG TASK
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
TASK...........: Add a mysqlbinlog option to filter certain kinds of statements
CREATION DATE..: Mon, 10 Aug 2009, 15:30
SUPERVISOR.....: Monty
IMPLEMENTOR....: 
COPIES TO......: 
CATEGORY.......: Client-BackLog
TASK ID........: 41 (http://askmonty.org/worklog/?tid=41)
VERSION........: Benchmarks-3.0
STATUS.........: Un-Assigned
PRIORITY.......: 60
WORKED HOURS...: 0
ESTIMATE.......: 0 (hours remain)
ORIG. ESTIMATE.: 0

PROGRESS NOTES:

-=-=(Psergey - Mon, 10 Aug 2009, 15:35)=-=-
High-Level Specification modified.
--- /tmp/wklog.41.old.12689     2009-08-10 15:35:04.000000000 +0300
+++ /tmp/wklog.41.new.12689     2009-08-10 15:35:04.000000000 +0300
@@ -1 +1,4 @@
-
+The implementation will depend on design choices made in WL#40:
+- If we decide to parse the statement, SQL-verb filtering will be trivial
+- If we decide not to parse the statement, we still can reliably distinguish the
+statement by matching the first characters against a set of patterns.

-=-=(Psergey - Mon, 10 Aug 2009, 15:31)=-=-
Dependency created: 39 now depends on 41



DESCRIPTION:

Add a mysqlbinlog option to filter certain kinds of statements, i.e. (syntax
subject to discussion):

  mysqlbinlog --exclude='alter table,drop table,alter database,...'



HIGH-LEVEL SPECIFICATION:



The implementation will depend on design choices made in WL#40:
- If we decide to parse the statement, SQL-verb filtering will be trivial
- If we decide not to parse the statement, we still can reliably distinguish the
statement by matching the first characters against a set of patterns.


ESTIMATED WORK TIME

ESTIMATED COMPLETION DATE
-----------------------------------------------------------------------
WorkLog (v3.5.9)