maria-developers team mailing list archive
-
maria-developers team
-
Mailing list archive
-
Message #00704
Updated (by Knielsen): Add a mysqlbinlog option to filter certain kinds of statements (41)
-----------------------------------------------------------------------
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:
-=-=(Knielsen - Fri, 14 Aug 2009, 14:17)=-=-
High-Level Specification modified.
--- /tmp/wklog.41.old.6963 2009-08-14 14:17:32.000000000 +0300
+++ /tmp/wklog.41.new.6963 2009-08-14 14:17:32.000000000 +0300
@@ -1,6 +1,11 @@
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
+
+Option 1:
+
+If we decide to parse the statement, SQL-verb filtering will be trivial
+
+Option 2:
+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.
If we chose the second, we'll have to perform certain normalization before
-=-=(Psergey - Mon, 10 Aug 2009, 15:47)=-=-
High-Level Specification modified.
--- /tmp/wklog.41.old.13282 2009-08-10 15:47:13.000000000 +0300
+++ /tmp/wklog.41.new.13282 2009-08-10 15:47:13.000000000 +0300
@@ -2,3 +2,10 @@
- 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.
+
+If we chose the second, we'll have to perform certain normalization before
+matching the patterns:
+ - Remove all comments from the command
+ - Remove all pre-space
+ - Compare the string case-insensitively
+ - etc
-=-=(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:
Option 1:
If we decide to parse the statement, SQL-verb filtering will be trivial
Option 2:
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.
If we chose the second, we'll have to perform certain normalization before
matching the patterns:
- Remove all comments from the command
- Remove all pre-space
- Compare the string case-insensitively
- etc
ESTIMATED WORK TIME
ESTIMATED COMPLETION DATE
-----------------------------------------------------------------------
WorkLog (v3.5.9)