Bug #84

Changeset #321 breaks compatability with sqlite

Added by dgtized-gmail-com - 1238 days ago. Updated 616 days ago.

Status :Closed Start :
Priority :High Due date :
Assigned to :tobi - % Done :

0%
Category :frontend
Target version :2.5
Resolution :

fixed

Description

in models/category.rb the function find_all_with_article_counters breaks compatability with sqlite. It appears that 
SELECT *, IF(article_id IS NULL, 0, COUNT(*)) AS article_counter

is not valid syntax in sqlite. Is there an alternate way to get this effect without using sub ifs?

History

07/12/2005 05:44 PM - scoop -

  • Status changed from New to Closed
  • Resolution set to fixed

(In r324) * Removed SQLite incompatibility in Category::find_all_with_article_counters (fixes #150)

07/12/2005 07:02 PM - Redmine Admin

  • Status changed from Closed to Feedback
  • Resolution deleted (fixed)

This still blows up in PostgreSQL. Can't do a "SELECT * FROM tbl GROUP BY col" unless everything in * is accounted for in the GROUP BY clause.

Patch will follow momentarily. Needs to be checked on sqlite and MySQL but should work.

07/12/2005 07:13 PM - scoop -

  • Status changed from Feedback to Closed
  • Resolution set to fixed

(In r325) * Changes in r324 broke Pgsql, fixed by this commit (closes #150) []

07/23/2005 09:20 AM - scoop -

  • Resolution set to fixed

(In r357) * Changes in r324 broke Pgsql, fixed by this commit (closes #150) []

  • Implemented BloggerAPI.newPost (closes #185, #79)
  • Added test coverage for BloggerAPI.getUserInfo
  • Reverted (accidential?) changes to User model in r354, making User tests pass again
  • Added test coverage for r354 and r355 making Configuration tests pass again
    Scott: Please be sure to run rake before committing and adjust tests according to your changes. Thanks.

Also available in: Atom PDF