tdbc::sqlite3

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

Artifact ID: a58e792e607b1e1fb41d06beba7d4a8d8bd0a759d9fd9db85635fab8667d999e
Ticket: 8d015d929f6294e2f77e7c580cb86e182f5508b5
tdbc::sqlite3 driver doesn't resolve duplicate names
User & Date: kbk 2019-09-13 17:15:05
Changes

  1. Change icomment to:

    You give as example the query:

        SELECT         fix_date,         home.tea_name,         away.tea_name     FROM     fixtures     JOIN     teams AS home ON home.tea_id = fix_home     JOIN     teams AS away ON away.tea_id = fix_away

    The way to work around it is to make sure that all the column names returned are distinct.

    SELECT fix_date, home.tea_name AS hometeam, away.tea_name AS awayteam FROM fixtures JOIN teams AS home ON home.tea_id = fix_home JOIN teams AS away ON away.tea_id = fix_away

    Now you don't have a name collision and you won't have a problem with one 'tea_name' overwriting another.

  2. Change login to "kbk"
  3. Change mimetype to "text/x-fossil-plain"