Uploaded image for project: 'AdMax'
  1. AdMax
  2. ADMAX-1525

User Settings: Account listed as both assigned and available to be assigned

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: unspecified
    • Fix Version/s: None
    • Component/s: Administrative Tools
    • Labels:
      None
    • Environment:

      Operating System: Windows XP
      Platform: PC

    • Bugzilla Id:
      2652

      Description

      Frank reported an incident - screen shot attached - where Avalon Bay was listed
      as both to be assigned and assigned to his account. I cannot duplicate this as
      him, me, or anyone else in the CCC, but looking at the debug I see:

      [Tue, 24 Feb 2009 11:23:44 -0800] (3) DATABASE: Created connection using
      "TSADatabaseConnectionFactory" factory

      [Tue, 24 Feb 2009 11:23:44 -0800] (3) DATABASE: caching "acct-st-tracker phpstdbrw"

      [Tue, 24 Feb 2009 11:23:44 -0800] (4) MYSQLDATABASE: Database::sql():
      [acctdb-01-write:3306:spike@st-tracker] => [create temporary table
      `st-tracker`.`tmp1`select distinct `accounts`.`id` from `tsacommon`.`accounts`
      left outer join `tsacommon`.`userAccountMap` on (`accounts`.`id` =
      `userAccountMap`.`accountID`) where (`userAccountMap`.`userID` = 216)]

      [Tue, 24 Feb 2009 11:23:44 -0800] (4) MYSQLDATABASE: [Explain]

      [Tue, 24 Feb 2009 11:23:44 -0800] (4) MYSQLDATABASE: Query executed in 0.0157
      seconds.

      [Tue, 24 Feb 2009 11:23:44 -0800] (4) MYSQLDATABASE: Database::sql(): returning []

      [Tue, 24 Feb 2009 11:23:44 -0800] (4) MYSQLDATABASE: Database::sql():
      [acctdb-01-write:3306:spike@st-tracker] => [select distinct `accounts`.`id`,
      `accounts`.`description` from `tsacommon`.`accounts` left outer join
      `st-tracker`.`tmp1` on (`accounts`.`id` = `st-tracker`.`tmp1`.`id`) where
      (`st-tracker`.`tmp1`.`id` is null) order by `accounts`.`description`]

      [Tue, 24 Feb 2009 11:23:44 -0800] (4) MYSQLDATABASE: [Explain]

      [Tue, 24 Feb 2009 11:23:44 -0800] (4) MYSQLDATABASE: Query executed in 0.0806
      seconds.

      [Tue, 24 Feb 2009 11:23:44 -0800] (4) MYSQLDATABASE: Query returned 167 row(s).

      [Tue, 24 Feb 2009 11:23:44 -0800] (4) MYSQLDATABASE: Database::sql(): returning
      [mysqli_result]

      [Tue, 24 Feb 2009 11:23:44 -0800] (4) MYSQLDATABASE: Database::sql():
      [acctdb-01-write:3306:spike@st-tracker] => [drop table `st-tracker`.`tmp1`]

      [Tue, 24 Feb 2009 11:23:44 -0800] (4) MYSQLDATABASE: [Explain]

      [Tue, 24 Feb 2009 11:23:44 -0800] (4) MYSQLDATABASE: Query executed in 0.0002
      seconds.

      [Tue, 24 Feb 2009 11:23:44 -0800] (4) MYSQLDATABASE: Database::sql(): returning []

      I am guessing if the last drop failed then this was re-run, the temp table used
      may be from the previous call? Dropping the previous temp table before calling
      create just to be sure may help prevent this if I am correct. If not, then let
      me know and I can play around with this a bit more.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              bduffy Bill Duffy (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: