I have to create databases at run time depending on the name of the new
user’s company and to run all the migrations for that new database.
for example: If a new user get registered and enter ABC as his company
name, then we will check if there is any existing user with same
company. If we dont have any user for that company then we have to
create a new Database and name it “ABC”. After creating this new
Database we have to run all the migration for this new Database.
All this has to be done at run time and dynamicaly.
I have to create databases at run time depending on the name of the new
user’s company and to run all the migrations for that new database.
for example: If a new user get registered and enter ABC as his company
name, then we will check if there is any existing user with same
company. If we dont have any user for that company then we have to
create a new Database and name it “ABC”. After creating this new
Database we have to run all the migration for this new Database.
Probably better not to do it this way. Have just one database but add
fields to differentiate which records in each table belong to each
user. The user will not be able to tell the difference between that
and your suggested solution.
Colin
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.