pt-find needs option to keep nulls
Bug #1063876 reported by
Joe
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Toolkit moved to https://jira.percona.com/projects/PT |
Triaged
|
Undecided
|
Unassigned |
Bug Description
pt-find Ver 2.1.4
On the pt-find page there is this example in the SYNOPSIS section.
pt-find --noquote --exec "INSERT INTO sysdata.tblsize(db, tbl, size) VALUES('%D', '%N', %T)"
When extending this to insert more of the available columns, such as the auto_increment column.
pt-find --noquote --exec "INSERT INTO sysdata.tblsize(db, tbl, size, auto_increment) VALUES('%D', '%N', %T, %a)"
You will get a sql syntax error for tables that don't contain an auto_increment column, because %a is replaced with a blank.
I propose a --[no]nulls option that will allow you to control what is replace in the case of a NULL value.
Changed in percona-toolkit: | |
status: | New → Triaged |
To post a comment you must log in.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/ /jira.percona. com/browse/ PT-1034