changed due to extended scope of the storage. For a whole set of additional features (Bookmarks, comments, SQL-history, tracking mechanism, PDF-generation, Transformations, Relations etc.) you need to create Since release 2.3.0 you can store comments to describe each column for each table. These will then be shown on the “printview”. Starting with release 2.5.0, comments are consequently used on the table pma__column_info) to update your PRE-2.5.0 Column_comments table use this: and remember that the Variable in config.inc.php has been renamed from $cfg['Servers'][$i]['column_comments'] to $cfg['Servers'][$i] ['column_info']

changed due to the extended scope of the storage. For a whole set of additional features (Bookmarks, comments, SQL-history, tracking mechanism, PDF-generation, Transformations, Relations etc.) you need to create Since release 2.3.0 you can store comments to describe each column for each table. These will then be shown on the “printview”. Starting with release 2.5.0, comments are consequently used on the table pma__column_info) to update your PRE-2.5.0 Column_comments table use this: and remember that the Variable in config.inc.php has been renamed from $cfg['Servers'][$i]['column_comments'] to $cfg['Servers'] [$i]['column_info']

changed due to the extended scope of the storage. For a whole set of additional features (Bookmarks, comments, SQL-history, tracking mechanism, PDF-generation, Transformations, Relations etc.) you need to create Since release 2.3.0 you can store comments to describe each column for each table. These will then be shown on the “printview”. Starting with release 2.5.0, comments are consequently used on the table pma__column_info) to update your PRE-2.5.0 Column_comments table use this: and remember that the Variable in config.inc.php has been renamed from $cfg['Servers'][$i]['column_comments'] to $cfg['Servers'] [$i]['column_info']

changed due to extended scope of the storage. For a whole set of additional features (Bookmarks, comments, SQL-history, tracking mechanism, PDF-generation, Transformations, Relations etc.) you need to create Since release 2.3.0 you can store comments to describe each column for each table. These will then be shown on the “printview”. Starting with release 2.5.0, comments are consequently used on the table pma__column_info) to update your PRE-2.5.0 Column_comments table use this: and remember that the Variable in config.inc.php has been renamed from $cfg['Servers'][$i]['column_comments'] to $cfg['Servers'][$i] ['column_info']

changed due to the extended scope of the storage. For a whole set of additional features (Bookmarks, comments, SQL-history, tracking mechanism, PDF-generation, Transformations, Relations etc.) you need to create Since release 2.3.0 you can store comments to describe each column for each table. These will then be shown on the “printview”. Starting with release 2.5.0, comments are consequently used on the table pma__column_info) to update your PRE-2.5.0 Column_comments table use this: and remember that the Variable in config.inc.php has been renamed from $cfg['Servers'][$i]['column_comments'] to $cfg['Servers'] [$i]['column_info']

changed due to extended scope of the storage. For a whole set of additional features (Bookmarks, comments, SQL-history, tracking mechanism, PDF-generation, Transformations, Relations etc.) you need to create Since release 2.3.0 you can store comments to describe each column for each table. These will then be shown on the “printview”. Starting with release 2.5.0, comments are consequently used on the table pma__column_info) to update your PRE-2.5.0 Column_comments table use this: and remember that the Variable in config.inc.php has been renamed from $cfg['Servers'][$i]['column_comments'] to $cfg['Servers'][$i] ['column_info']

changed due to the extended scope of the storage. For a whole set of additional features (Bookmarks, comments, SQL-history, tracking mechanism, PDF-generation, Transformations, Relations etc.) you need to create Since release 2.3.0 you can store comments to describe each column for each table. These will then be shown on the “printview”. Starting with release 2.5.0, comments are consequently used on the table pma__column_info) to update your PRE-2.5.0 Column_comments table use this: and remember that the Variable in config.inc.php has been renamed from $cfg['Servers'][$i]['column_comments'] to $cfg['Servers'][$i] ['column_info']

changed due to extended scope of the storage. For a whole set of additional features (Bookmarks, comments, SQL-history, tracking mechanism, PDF-generation, Transformations, Relations etc.) you need to create Since release 2.3.0 you can store comments to describe each column for each table. These will then be shown on the “printview”. Starting with release 2.5.0, comments are consequently used on the table pma__column_info) to update your PRE-2.5.0 Column_comments table use this: and remember that the Variable in config.inc.php has been renamed from $cfg['Servers'][$i]['column_comments'] to $cfg['Servers'][$i] ['column_info']

changed due to extended scope of the storage. For a whole set of additional features (Bookmarks, comments, SQL-history, tracking mechanism, PDF-generation, Transformations, Relations etc.) you need to create Since release 2.3.0 you can store comments to describe each column for each table. These will then be shown on the “printview”. Starting with release 2.5.0, comments are consequently used on the table pma__column_info) to update your PRE-2.5.0 Column_comments table use this: and remember that the Variable in config.inc.php has been renamed from $cfg['Servers'][$i]['column_comments'] to $cfg['Servers'][$i] ['column_info']

changed due to extended scope of the storage. For a whole set of additional features (Bookmarks, comments, SQL-history, tracking mechanism, PDF-generation, Transformations, Relations etc.) you need to create Since release 2.3.0 you can store comments to describe each column for each table. These will then be shown on the “printview”. Starting with release 2.5.0, comments are consequently used on the table pma__column_info) to update your PRE-2.5.0 Column_comments table use this: and remember that the Variable in config.inc.php has been renamed from $cfg['Servers'][$i]['column_comments'] to $cfg['Servers'][$i] ['column_info']