79439

79439



Backward Compatibility

Considerations of backward compatibility only apply when using a recent version of InnoDB (the

InnoDB Plugin, or MySQL 5.5 and higher with InnoDB 1.1) alongside an older one (MySQL 5.1 or

earlier, with the built-in InnoDB rather than the InnoDB Plugin). To minimize the chance of compatibility

issues, you can standardize on the InnoDB Plugin for all your MySQL 5.1 and earlier database servers.

In generał, a newer version of InnoDB may create a table or index that cannot safely be read or written

with a prior version of InnoDB without risk of crashes, hangs, wrong results or corruptions. InnoDB 1.1

includes a mechanism to guard against these conditions, and to help preserve compatibility among

database files and versions of InnoDB. This mechanism lets you take advantage of some new features

of an InnoDB release (such as performance improvements and bug fixes), and still preserve the option

of using your database with a prior version of InnoDB, by preventing

accidental use of new features

that create downward-incompatible disk files.

If a version of InnoDB supports a particular file format (whether or not that format is the default), you

can query and update any table that requires that format or an earlier format. Only the creation of

new tables using new features is limited based on the particular file format enabled. Conversely, if

a tablespace contains a table or index that uses a file format that is not supported by the currently

running software, it cannot be accessed at all, even for read access.

The only way to “downgrade” an InnoDB tablespace to an earlier file format is to copy the data to a new

table, in a tablespace that uses the earlier format. This can be done with the alter table statement,

as described in Section 5.4.7.4, “Downgrading the File Format".

The easiest way to determine the file format of an existing InnoDB tablespace is to examine the

properties of the table it contains, using the show table status command or querying the table

INFORMATION_SCHEMA.TABLES. If the Row_format of the table is reported as 'Compressed'



Wyszukiwarka

Podobne podstrony:
279 The ore body geometry parameters as regards consideration of economic comparison on the basis of
img117 “Carriere, Beate, P.T. and Linda Felix, P.T. “In Consideration of Proportions.” PT Magazine A
compact and redundant Row Formats Early versions of InnoDB used an unnamed file format (now called A
Overview of InnoDB Row Storage The storage for rows and associated columns affects performance for q
Federated Storage Engine Notes and Tips You should be aware of the foliowing points when using the F
Handling MySQL Recovery with ZFS When using ZFS replication to provide a constant copy of your data,
memcached Deployment When using memcached you can use a number of different potential deployment str
Statement-based replication. When using statement-based replication, a simple rule of thumb to follo
Using GTlDs for Failover and Scaleout There are a number of techniques when using MySQL Replication
GIYING PERSONAL INFORMATION1JIOW DO YOU LIKE SPENDING YOUR HOLIDA YS? Holidays is mostly the only ti
GCT01G01 BMP USING THE MOUSE Screen 1 of 3 When using the mouse, make surę the córci is aimeci direc
ZSBD 4 SQL Server and in all databases. It is provided for backward compatibility and should not be
214 JAN KIENIEWICZ, MARCIN KULA It is only by comparing different variants of regression into backwa
F e a r Perseus Mandate Custom front COMPACT 10010732 G III lllllll llllll Thi* software Is only

więcej podobnych podstron