will not be saved either). Note For transactions to work correctly in MySQL your tables must use InnoDB engine. Remember that MyISAM tables do not support transactions. Let’s see how we can use saveAssociated() 'post_id' => array('column' => 'post_id'), ), 'tableParameters' => array( 'engine' => 'InnoDB', 'charset' => 'latin1', 'collate' => 'latin1_general_ci' ) ); is an example of 'post_id' => array('column' => 'post_id'), ), 'tableParameters' => array( 'engine' => 'InnoDB', 'charset' => 'latin1', 'collate' => 'latin1_general_ci' ) ); is an example of

will not be saved either). Note: For transactions to work correctly in MySQL your tables must use InnoDB engine. Remember that MyISAM tables do not support transactions. Let’s see how we can use saveAssociated() => true), 'post_id' => array('column' => 'post_id'), ), 'tableParameters' => array( 'engine' => 'InnoDB', 'charset' => 'latin1', 'collate' => 'latin1_general_ci' ) ); is an example of a table using tableParameters => true), 'post_id' => array('column' => 'post_id'), ), 'tableParameters' => array( 'engine' => 'InnoDB', 'charset' => 'latin1', 'collate' => 'latin1_general_ci' ) ); is an example of a table using tableParameters

structure in MySQL. The following could be used to add table options: $schema->options([ 'engine' => 'InnoDB', 'collate' => 'utf8_unicode_ci', ]); Platform dialects only handle the keys they are interested use bytea instead of blob `expires` int(10) unsigned DEFAULT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; You can find a copy of the schema for the sessions table in the application

structure in MySQL. The following could be used to add table options: $schema->options([ 'engine' => 'InnoDB', 'collate' => 'utf8_unicode_ci', ]); Platform dialects only handle the keys they are interested PostgreSQL use bytea instead of blob �expires� int(10) unsigned DEFAULT NULL, PRIMARY KEY (�id�) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; You can find a copy of the schema for the sessions table in the application

structure in MySQL. The following could be used to add table options: $schema->options([ 'engine' => 'InnoDB', 'collate' => 'utf8_unicode_ci', ]); Platform dialects only handle the keys they are interested use bytea instead of blob `expires` int(10) unsigned DEFAULT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; You can find a copy of the schema for the sessions table in the application

structure in MySQL. The following could be used to add table options: $schema->options([ 'engine' => 'InnoDB', 'collate' => 'utf8_unicode_ci', ]); Platform dialects only handle the keys they are interested PostgreSQL use bytea instead of blob �expires� int(10) unsigned DEFAULT NULL, PRIMARY KEY (�id�) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; You can find a copy of the schema for the sessions table in the application

structure in MySQL. The following could be used to add table options: $schema->options([ 'engine' => 'InnoDB', 'collate' => 'utf8_unicode_ci', ]); Platform dialects only handle the keys they are interested use bytea instead of blob `expires` int(10) unsigned DEFAULT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; You can find a copy of the schema for the sessions table in the application

structure in MySQL. The following could be used to add table options: $schema->options([ 'engine' => 'InnoDB', 'collate' => 'utf8_unicode_ci', ]); Platform dialects only handle the keys they are interested PostgreSQL use bytea instead of blob �expires� int(10) unsigned DEFAULT NULL, PRIMARY KEY (�id�) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; You can find a copy of the schema for the sessions table in the application