Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 705669
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 14, 20262026-05-14T04:04:47+00:00 2026-05-14T04:04:47+00:00

I recently upgraded MySQL to 5.1.41. Before the upgrade the following SQL worked (or

  • 0

I recently upgraded MySQL to 5.1.41. Before the upgrade the following SQL worked (or at least I thought I remembered it working…it has been a few weeks since designing this…). Now the SQL gives me an error stating that the “archived” column is ambiguous. How can I write this differently, or is there a different problem I’m not aware of?

I simply want to return the “unit_id”, “lease_count” (stored in another table with a unit_id that should correspond with the “a.unit_id”), and “lease_archived_count (stored in another table with a unit_id that should correspond with the “a.unit_id”).

SELECT a.unit_id, 
    (SELECT count(*) FROM o_leases WHERE unit_id = a.unit_id AND archived = 0) as lease_count, 
    (SELECT count(*) FROM o_leases WHERE unit_id = a.unit_id AND archived = 1) as lease_archive_count

FROM p_unit a, properties b, portfolio c 

WHERE a.property_id = b.properties_id 
AND b.portfolio_id = c.portfolio_id 
AND a.archived = 0 

Thanks for your help.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-14T04:04:47+00:00Added an answer on May 14, 2026 at 4:04 am

    There can only be one place where this error is referring to. I suggest to give the tables in the sub select also an alias:

    (SELECT count(*) FROM o_leases o WHERE o.unit_id = a.unit_id AND o.archived = 0) as lease_count, 
    (SELECT count(*) FROM o_leases o WHERE o.unit_id = a.unit_id AND o.archived = 1) as lease_archive_count
    

    It seems that it collides with the archived field of p_unit.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am getting following error. Restore failed for Server I have recently upgraded SQL
I recently upgraded to eclipse indigo from galileo. There has been some changes in
I'm currently working with a rails 3.0.x app that's recently been upgraded from rails
I recently upgraded to Oracle Sql Developer 2.1 It's far better, but the query
I recently upgraded to CodeIgniter 2.1. The below model code (machforms_model.php) was properly working
I recently upgraded my Silverlight app from 3 to 4. After a few hours
I just recently upgraded to MySQL 5.1.6 in order to take advantage of the
I recently upgraded Xcode from 3.2 to 4.2. After the upgrade I was having
I've recently upgraded to OS X 10.7.4 from Snow Leopard. Since then, MySQL can't
I have recently upgraded my gemfile to try and get Rails 3.1 working with

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.