Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I dont fully understand your question., like</p> <ol> <li>what is the problem you are facing right now using mongo and MySQL in same app, and </li> <li>whats the reason for going multiple rails app dealing with different dbs.</li> </ol> <p>Though am not an expert in ruby &amp; rails(picked up few months ago), i like to add something here.</p> <p>I am currently building the rails app utilizing both mongo and MySQL in the back end. Mongoid &amp; ActiveRecord are the drivers. MySql for transactions and mongo for all other kind of data (geo spatial mainly). Its just straight forward. You can create different models inheriting from mongoid and activerecord. </p> <pre><code>class Item include Mongoid::Document field :name, :type =&gt; String field :category, :type =&gt; String end </code></pre> <p>and</p> <pre><code>class User &lt; ActiveRecord::Base end </code></pre> <p>And you can query both the way same way (except complex sql joins, also mongoid has some addition querying patterns for Geo spatial kind of queries)</p> <pre><code>Item.where(:category =&gt; 'car').skip(0).limit(10) User.where(:name =&gt; 'ram') </code></pre> <p>Its a breeze. But there are some important points you need to know</p> <ol> <li>Create your Active record models before the mongoid models. Once mongoid is activated (on rails g mongoid:config - mongoid.yml added) all the scaffolding , and generations works toward mongo db. Otherwise every time you need to delete the mongoid.yml before creating the Activerecord models</li> <li>And don't use mongoid in a relational way. i know mongoid provides lot of options to define realtions. Like Belongs_to relations stores the refernece id's in child documents. Its quite opposite to the mongo DbRef. Its greatly confusing when leaving the mongo idioms for the favour of active record feel. So try to stick with the document nature of it. Use embed and DbRef whenever necessary. (may be someone corrcet me if am wrong)</li> </ol> <p>Still Mongoid is a great work. Its fully loaded with features.</p>
    singulars
    1. This table or related slice is empty.
    1. PORails: mixing NOSQL & SQL Databases
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USRameshVel
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYes, seems it works actually ..., with some implied steps as following: I put in place the modification, starting from a previous, fully functional Rails 3.0.7 app, bundled at first with mongoid. 1) add gem ‘mysql2’ (or others adapter like sqlite3) to Gemfile & run bundle 2) add require "active_record/railtie" & require "rails/test_unit/railtie" to config/application.rb 3) add config/database.yml (living together with config/mongodb.ym)
      singulars
      1. PO
      1. USLuca G. Soave
    2. CO... my reason for going multiple rails app (engines or sinatra endpoints) dealing with different dbs was: (1) encapsulation for better maintenance/upgrading, (2) modularity for reusing eventually in other apps, (3) readability & so on. Of course that is vs simplicity but it seems the last win !
      singulars
      1. PO
      1. USLuca G. Soave
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload