By default a query is assumed to make the array key the id of the primary key field. This caused problems with other developers before as it assumes that the primary field will be unique and auto-incremented. I think the logic behind this is very limited and will in the future cause other potential bugs. The current bug I am battling is this:
Assuming we dont have an id field and only have to key field, something like this:
By default a query is assumed to make the array key the id of the primary key field. This caused problems with other developers before as it assumes that the primary field will be unique and auto-incremented. I think the logic behind this is very limited and will in the future cause other potential bugs. The current bug I am battling is this:
Assuming we dont have an id field and only have to key field, something like this:
CREATE TABLE `pds_core_ user_role_ permissions` ( role_id` ,`menu_ id`)
`user_role_id` int(10) NOT NULL DEFAULT '0',
`menu_id` varchar(32) NOT NULL,
PRIMARY KEY (`user_
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
Assuming we add values like these,
INSERT INTO pds_core_ user_role_ permissions VALUES ('1', '1016054546'); user_role_ permissions VALUES ('1', '1210756465'); user_role_ permissions VALUES ('1', '131201277'); user_role_ permissions VALUES ('1', '1363712008'); user_role_ permissions VALUES ('1', '1405303115'); user_role_ permissions VALUES ('1', '1411278578'); user_role_ permissions VALUES ('1', '1440418834');
INSERT INTO pds_core_
INSERT INTO pds_core_
INSERT INTO pds_core_
INSERT INTO pds_core_
INSERT INTO pds_core_
INSERT INTO pds_core_
Now the system will only return a single row as __auto__ assumed incorrectly.