tdbc::sqlite3

Ticket Change Details
Login
Bounty program for improvements to Tcl and certain Tcl packages.
Overview

Artifact ID: 434b61b1277ae0a61d8c0d373635ec76414875d54d833de537b748daabc5fb33
Ticket: a1e76ad92f66d02fa7eb75b4d0d1231a382677ca
columns metadata method always reports column names in lower case
User & Date: chw 2020-05-26 16:03:04
Changes

  1. Change foundin to "current"
  2. Change icomment to:

    The connection method "columns" reports the column names of a given table but the column names are reformatted to lower case with "string tolower". When data later is retrieved, that reformat on column names is not performed, i.e. the dict receiving the row data of a result set can have mixed case column names. Why is this asymmetric behavior? Would it be symmetric, the column method could easily be used to construct SQL programmatically, e.g. to build up the bind parameter names for an INSERT statement which then map to the dict keys of a row of a result set. Or am I missing a subtle detail?

  3. Change login to "chw"
  4. Change mimetype to "text/plain"
  5. Change private_contact to "0b3aff16612e1e9f3b675963fa64e01bd1d89307"
  6. Change severity to "Important"
  7. Change status to "Open"
  8. Change title to:

    columns metadata method always reports column names in lower case

  9. Change type to "Code_Defect"