Bug #1813
Change database to hold bigger objects
| Status: | Closed | Start date: | 03/15/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | Release 4.0 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 3.8 |
Description
Objects are serialized to the database as xml in a text column. In MySQL this column can hold up to 64 Kb. This column should be changed in MySQL to support bigger objects.
Associated revisions
bug #1813: Storage type for BODY columns is now MEDIUMTEXT (this is only relevant for MySQL DBs)
bug #1813: Storage type for BODY columns is now MEDIUMTEXT (this is only relevant for MySQL DBs)
(cherry picked from commit b68a8b6c83bdc6afb88febfb5ce304e57c20dd7b)
Bug #1813: Add migrator to 3.8.4
Bug #1813: Add migrator to 3.8.4
(cherry picked from commit 02a3959d13be219081b3e7149d0e599fc90349bc)
Conflicts:
install.sh
Bug #1813: Rename last migrator to 3.8.4_to_3.9.80.rb
Bug #1813: Update column types in onedb fsck
bug #1813: Storage type for BODY columns is now MEDIUMTEXT (this is only relevant for MySQL DBs)
(cherry picked from commit b68a8b6c83bdc6afb88febfb5ce304e57c20dd7b)
Conflicts:
src/nebula/Nebula.cc
src/nebula/SystemDB.cc
src/vnm/VirtualNetwork.cc
bug #1813: Include SystemDB files, now separated from nebula.cc implementation as in 4.x
Bug #1813: Update column types in onedb fsck
(cherry picked from commit ab7ad5d56c42a410c865f6503dcd4a996df926b6)
Conflicts:
src/onedb/fsck.rb
History
#1
Updated by Ruben S. Montero over 8 years ago
- Status changed from New to Closed
- Target version set to Release 4.0
- Resolution set to fixed