Project

General

Profile

Bug #11

Reports fails to import when using MySQL database

Added by Ohad Levy over 9 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Importers
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

the current schema generates in MySQL mediumtext, while in order for serialization to work you need text.

quick workaround:

ALTER TABLE reports MODIFY log text;

Associated revisions

Revision d64a48f9 (diff)
Added by Dominic Cleal almost 6 years ago

Change operatingsystem to osfamily for Fedora etc

Fixes #11

History

#1 Updated by Ohad Levy over 9 years ago

  • Status changed from New to Ready For Testing
  • % Done changed from 0 to 100

#2 Updated by Moty Lavi over 9 years ago

Still having problem to migrate reports to my MySQL db.

I can not find any log of the problem except that my reports are empty...

#3 Updated by Ohad Levy over 9 years ago

motyla wrote:

Still having problem to migrate reports to my MySQL db.

I can not find any log of the problem except that my reports are empty...

can you elaborate in some way?
Did you install the custom report in puppet? (in the extra directory?)

#4 Updated by Moty Lavi over 9 years ago

Ok .... my mistake ..... I had some syntax problem at puppet.conf reports entry ....

sorry :-)

#5 Updated by Ohad Levy over 9 years ago

#6 Updated by Ohad Levy over 9 years ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF