Checking the actual database

Let's take a quick look at the database itself to see what happened during the execution of the app. Since the server is currently up and running, we can connect to it using the Mongo shell-a command line interface to the MongoDB server. Execute the following commands to connect to the server using Mongo and run a query against the chapter's collection. As you can see in the upcoming code, Mongo shell connects to a default database named test initially. We need to manually specify the database name to switch to if it's something other than test:

    $ mongo
    MongoDB shell version: 2.4.8
    connecting to: test
    > use myproject
    > show collections
    chapters
    system.indexes
    > db.chapters.find().pretty()  
Here, pretty is used as part of the command to format the result from the find command. This is used only in a shell context. It does more of a prettification task for the JSON.

You should see something similar to the following output:

{  
    'id' : ObjectId("5547e734cdf16a5ca59531a7"), 
    'Title': 'Snow Crash',  
    'Author': 'Neal Stephenson'  
}, 
{  
    'id' : ObjectId("5547e734cdf16a5ca59531a7"), 
    'Title': 'Snow Crash',  
    'Author': 'Neal Stephenson' 
} 
If you run the Node app again, the records will be inserted into the Mongo server again. So, if you repeat the command multiple times, the result will have more records in the output. We are not handling this case in this chapter as we intend to have only specific code, that will be simple enough to understand.
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
18.118.128.105