Issue #3099 has been updated by Rein Henrichs. Priority changed from Normal to High Target version changed from 1.1 to 1.2
---------------------------------------- Bug #3099: Non-portable SQL used in status model http://projects.puppetlabs.com/issues/3099 Author: Andrew Forgue Status: Accepted Priority: High Assigned to: Category: Target version: 1.2 Keywords: Branch: Affected URL: I'm trying to try out Dashboard on PostgreSQL and I found that app/models/status.rb uses some non-portable (anything other than MySQL) SQL in the by_interval function. Specifically: SUM(success) -- It makes no sense to sum a boolean value and should do COUNT(*) WHERE success=true UNIX_TIMESTAMP() -- Is MySQL specific, PostgreSQL uses extract('epoch' from time), and others, I don't know about Looking at the query I don't think this SQL is something that can be translated to activerecord and probabably has to be done in ruby itself. I saw in the changelog: 86e93c3 Dashboard now requires MySQL I think this is not good considering storeconfigs are supported in PostgreSQL. I really really don't want to run 2 different RDBMSs for the same software. Thanks -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
