[dev.icinga.com #3951] Extend Cronk xml column in database to allow big Cronks to be saved (MySQL only)

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/3951

Created by mfrosch on 2013-04-11 09:00:28 +00:00

Assignee: mfrosch Status: Resolved (closed on 2013-04-11 10:09:14 +00:00) Target Version: 1.9 Last Update: 2013-04-11 10:30:18 +00:00 (in Redmine)

Icinga Version: 1.8.4
Icinga Web Version: 1.9.0-dev
IDO Version: 1.8.4
OS Version: Debian/wheezy
DB Type: MySQL
DB Version: 5.5.30+dfsg-1
Browser Version: all

---

The cronk_xml column in the database is currently a TEXT by default.

This causes problems when trying to save Cronks with big amounts of data, e.g. inGraph.

Our plan is to switch to "LONGTEXT" in MySQL.

PgSQL: TEXT is "unlimited" by default - http://www.postgresql.org/docs/8.0/static/datatype-character.html Oracle: CLOB can hold up to 4GB of Data - http://www.orafaq.com/wiki/CLOB

Changesets

2013-04-11 10:08:15 +00:00 by mfrosch 8cf155675cc29f2b9ae6104ccd24e876106b2486

Extend Cronk xml column in database to allow big Cronks to be saved

We are using LONGTEXT instead of TEXT now (MySQL only)

fixes #3951

[icinga-migration]

Updated by mfrosch on 2013-04-11 09:03:56 +00:00

Clarification: This only needs to be changed in MySQL, the field in PgSQL and Oracle should be fine for now!

[icinga-migration]

Updated by mfrosch on 2013-04-11 10:08:09 +00:00

Unfortunatly this won't be possible with Doctrine, when using make create-db it will still create the table with a TEXT column.

We would need to patch Doctrine for this.

So anyone who creates the schema via make create-db in versions >= 1.9 might want to execute this statement:

ALTER TABLE cronk MODIFY COLUMN cronk_xml LONGTEXT;

[icinga-migration]

Updated by mfrosch on 2013-04-11 10:09:14 +00:00

• Status changed from Assigned to Resolved
• Done % changed from 0 to 100

Applied in changeset 8cf155675cc29f2b9ae6104ccd24e876106b2486.

[icinga-migration]

Updated by mfrosch on 2013-04-11 10:30:18 +00:00

*The update will like any usual SQL Update for Icinga Web!