# Concept: using 2 databases in one project or how to sepaarate migrations

**URL:** <https://www.ruby-forum.com/t/concept-using-2-databases-in-one-project-or-how-to-sepaarate-migrations/149409>\
**Category:** Rails\
**Created:** [September 24, 2008, 3:27pm UTC](https://www.ruby-forum.com/t/concept-using-2-databases-in-one-project-or-how-to-sepaarate-migrations/149409 "2008-09-24T15:27:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Fritzek](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/f/d6d6ee/32.png) [@Fritzek](https://www.ruby-forum.com/u/Fritzek)\
**Post date:** [September 24, 2008, 3:27pm UTC](https://www.ruby-forum.com/t/concept-using-2-databases-in-one-project-or-how-to-sepaarate-migrations/149409/1 "2008-09-24T15:27:00Z")

</div>

Hi folks

just a question of concept about using 2 databases for the same  
project.  
Situation: running a project which uses a plugin with its own database  
structure, migrations and initial data loads, now I want to extend the  
functionality of this plugin using my own models, db objects,  
migrations etc. in addition to the objects coming with the plugin.  
Running this in one db will give you problems regarding the migrations  
etc.