Khelender Sasan

I've infact done the migration and its not working after that See the existence of tables in run below where the incorrect join of table names may be there. (a table with name of subjectusers is getting created instead of subjects_users) See run below to see incorrect table name generation mysql> use virtx Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changed mysql> show tables ; +-------------------+ | Tables_in_virtx...

I've infact done the migration see the existence of tables and comment where the incorrect join of table names may be there. (a table with name of subjectusers is getting created instead of subjects_users) See run below to see incorrect table name generation mysql> use virtx Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changed mysql> show tables ; +-------------------+ | Tables_in_virtx | +-------------------+...

I have worked briefly on making VirtualX available on Docker system. See following URLs https://hub.docker.com/r/sasan/virtualx/ https://github.com/ksasan/docker/tree/master/recipes/virtualx If any one is interested in using this / further enabling this, we can talk.

Any update? Getting same problem ApplicationController::current_user ApplicationController::current_user_session ^[[1m^[[36mSQL (0.7ms)^[[0m ^[[1mdescribe subjects_users^[[0m Mysql::Error: Table 'virtualx.subjects_users' doesn't exist: describe subjects_users