I would like to know what is the major reason to change the auth assignment table structure on yii 2.0 (if there is any)
both table structures are as below,
create table AuthAssignment[/size]
itemname varchar(64) not null,
userid varchar(64) not null,
primary key (itemname,userid),
foreign key (itemname) references AuthItem (name) on delete cascade on update cascade
create table `tbl_auth_assignment`
`item_name` varchar(64) not null,
`user_id` varchar(64) not null,
primary key (`item_name`,`user_id`),
foreign key (`item_name`) references `tbl_auth_item` (`name`) on delete cascade on update cascade) engine InnoDB;
my concern is, [size=“2”] why [/size]column[size=“2”] naming conventions are changed… for ex: column [/size]changed[size=“2”] from ‘userid’ to 'user_id[/size][size=“2”]’ (any special reason ?)[/size]
[size=“2”]normally when we generate the model we get all the columns as attributes so [/size]wouldn’t[size=“2”] it be nice to leave it the same way ? i juts like to know what kind of advantages could be hidden inside this transition of table [/size]structure[size=“2”]… [/size]
It makes sense. The names now follow Yii’s own standards.
Please don’t expect BC: although the team said that they will try to make the transition as easy as possible, this is a major new version, rewrote from the scratch.
I’m sure that the core team will make every effort to bring architectural improvements to Yii 2.0. This will require changes. Please don’t regard these changes as BC-breaking, since there are no hard BC promises.