docstr: http://bugs.python.org/issue14720
  
  The microsecond parsing of convert_timestamp() should pad with zeros,
  since the microsecond string "456" actually represents "456000".
code: def test_convert_timestamp_microsecond_padding(self):
      """
      http://bugs.python.org/issue14720
  
      The microsecond parsing of convert_timestamp() should pad with zeros,
      since the microsecond string "456" actually represents "456000".
      """
  
      with memory_database(detect_types=sqlite.PARSE_DECLTYPES) as con:
          cur = con.cursor()
          cur.execute("CREATE TABLE t (x TIMESTAMP)")
  
          # Microseconds should be 456000
          cur.execute(
              "INSERT INTO t (x) VALUES ('2012-04-04 15:06:00.456')"
          )
  
          # Microseconds should be truncated to 123456
          cur.execute(
              "INSERT INTO t (x) VALUES ('2012-04-04 15:06:00.123456789')"
          )
  
          cur.execute("SELECT * FROM t")
          with self.assertWarnsRegex(DeprecationWarning, "converter"):
              values = [x[0] for x in cur.fetchall()]
  
          self.assertEqual(
              values,
              [
                  datetime.datetime(2012, 4, 4, 15, 6, 0, 456000),
                  datetime.datetime(2012, 4, 4, 15, 6, 0, 123456),
              ],
          )
  
imports: import datetime
  import unittest
  import sqlite3
  import weakref
  import functools
  from test import support
  from unittest.mock import patch
  from .util import memory_database, cx_limit
  from .util import MemoryDatabaseMixin
label_desc: Use image node_id 22 for calling the RegressionTests obj's underlying member method code with example usage: obj.test_convert_timestamp_microsecond_padding() without return types