Best practice for starting for building your DB?

Hi,

Im just starting RoR so forgive me if I ask some stupid questions. Is
it easier to create the a DB with a couple of tables through ruby on
rails or can I just as easily work with the DB if I already created it
through a front end app like HeidiSQL?

Besides that rails generates migrations for you which is a very useful
feature as you can rollback the changes in your database if they don’t
satisfy you…

On 25 Kwi, 23:19, Shandy N. [email protected]

[email protected] wrote:

Hi,

Im just starting RoR so forgive me if I ask some stupid questions. Is
it easier to create the a DB with a couple of tables through ruby on
rails or can I just as easily work with the DB if I already created it
through a front end app like HeidiSQL?

It should work either way, but rails apps need to have a column called
id for every table and that id needs to be the key. As long as you have
that for all your tables you should be golden. It would, however, be a
good idea to create your tables - if you can - using rails because it
can automagically generate the structure for you and in that way you can
insure that the tables were constructed properly.

-S

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs