pt-find needs option to keep nulls

Reported by Joe on 2012-10-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit
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.

Joe (joegrasse) wrote :
Changed in percona-toolkit:
status: New → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers