Project

General

Profile

Actions

Bug #11

closed

Reports fails to import when using MySQL database

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

Status:
Closed
Priority:
Normal
Assignee:
Category:
Importers
Target version:
Difficulty:
Triaged:
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;

Actions #1

Updated by Ohad Levy over 14 years ago

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

Updated by Moty Lavi over 14 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...

Actions #3

Updated by Ohad Levy over 14 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?)

Actions #4

Updated by Moty Lavi over 14 years ago

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

sorry :-)

Actions #5

Updated by Ohad Levy over 14 years ago

Actions #6

Updated by Ohad Levy over 14 years ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF