Puppet » Puppet Dashboard

SQLite3 also fails. DB initialization works, but once you try to access through the web interface:

SQLite3::SQLException: no such function: UNIX_TIMESTAMP: SELECT

    COUNT(*) - SUM(success) as failed,
    COUNT(*) as total,
    SUM(success) / COUNT(*) * 100 as percent,
    FROM_UNIXTIME(FLOOR(UNIX_TIMESTAMP(time) / 300) * 300) as start
  FROM reports

GROUP BY FLOOR(UNIX_TIMESTAMP(time) / 300) LIMIT 100

Andrew Forgue writes in #3099:

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

Christian: Sorry about that, thanks for re-opening this.

The new rake db:raw:optimize task only has support for MySQL. It should be extended to support PostgreSQL'sVACUUM ANALYZE. The code is atlib/tasks/db_raw.rake`.

Can we find out if this was done for PE2.0? We would like to drop MySQL if possible as the rest of our infrastructure is Postgresql.

I’m sorry Neal, this won’t be done for PE 2.0, but it’s an important target feature for a subsequent release.