The disadvantage of InnoDB, that you will have to backup more often, also InnoDB has its own separate storage place (file), in case it is lost, you won't be able to restore it. In this regard MyISAM has more flexible restoration workflow.
you can google more detailed info.
http://www.oxwall.org/forum/topic/35946?page=1#post-145108
maybe I need more time in order to understand the relationship among ow_base_question_data, ow_base_question_value and ow_base_question
Infact I do not understand 'cause we have the columns "questionName" and ow_base_question."name" not in clear mode: we have great varchars /values full of numbers and characters so it's difficult to retrieve the values that we see on the pages..
Moonwald
For example I have into ow_base_question_value VALUES (questionName) without a precise meaning
INSERT INTO `ow_base_question_value` VALUES (309,'4971fc7002dca728f9a7f2a417c5284e',512,4);INSERT INTO `ow_base_question_value` VALUES (310,'match_sex',1,0);INSERT INTO `ow_base_question_value` VALUES (311,'match_sex',2,1);
I have the same into ow_base_question_dataow_base_question_datado you know why?
taking your past query:SELECT u.username, d.`intValue` as 'match_sex', d1.`textValue` as 'realname', d2.`dateValue` as 'birthdate' FROM ow_base_user u
INNER JOIN ow_base_question_data d ON ( u.id = d.userId and d.questionName = 'match_sex' )
INNER JOIN ow_base_question_data d1 ON ( u.id = d1.userId and d1.questionName = 'realname' )
INNER JOIN ow_base_question_data d2 ON ( u.id = d2.userId and d2.questionName = 'birthdate' )
what does it need to add in this query in order to know value/values the key/keys associated with a specific multiple choice and the relative section profile question of all users?