Refactor #80: Reports data should be accessed in a simple way - Foreman

Actions

Copy link

Refactor #80

closed

Reports data should be accessed in a simple way

Added by Ohad Levy about 15 years ago. Updated about 15 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Ohad Levy

Category:

Puppet Reports

Target version:

0.1-3

Difficulty:

Triaged:

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

Currently report status is stored in one integer, it should be broken down into multiple database tables allowing to reduce the size of the database (by not storing the entire Puppet::Transaction::Report).

this should allow to search in a more rails way for all hosts that has a report with change count > 20

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Ohad Levy about 15 years ago

Target version deleted (~~0.1-3~~)

as the new version of puppet is going to be a massive rewrite of how reports are handled, I'm going to push this db schema changes until its clear what info puppet will provide.

additionally, I was never really happy with my ideas for the schema structure, so any ideas are welcomed.

Actions

Copy link

Updated by Ohad Levy about 15 years ago

I've created http://github.com/ohadlevy/foreman/tree/report_scopes

I think it solves all of the topics in this issue without changing the database schema - I'll appreciate a code review :)

Actions

Copy link

Updated by Ohad Levy about 15 years ago

Ohad Levy wrote:

I've created http://github.com/ohadlevy/foreman/tree/report_scopes

I think it solves all of the topics in this issue without changing the database schema - I'll appreciate a code review :)

well.. I've just learned that indexes do not work on bitwise columns.. even though I really like that code...

Actions

Copy link