Skip to main content

MongoDB - Relationships

It's represent how several types of documents are logically related to each other. Relationship can be pattern via embedded and referenced approaches like  1:1, 1: N, N: 1 or N: N.

We will consider the example of storing addresses for users. Suppose one user can have multiple addresses making this a 1:N relationship.
Following is the sample document structure of user document:

{
   "_id":ObjectId("52mmm33cd85242f436000001"),
   "name": "Dilip",
   "contact": "987654321",
   "dob": "01-01-1991"
}


given below  is the sample document structure of address document:

{
   "_id":ObjectId("52ffc4a5d85242602e000054"),
   "building": "22 A",
   "pincode": 123456,
   "city": "Delhi",
   "state": "Delhi"
}


Modeling Embedded Relationships
In this approach, we will set the address document inside the user document.


{
   "_id":ObjectId("52mmm33cd85242f436000001"),
   "contact": "987654321",
   "dob": "01-01-1991",
   "name": "Dilip",
   "address": [
      {
         "building": "E-234",
         "pincode": 110096,
         "city": "Delhi",
         "state": "Delhi"
      },
      {
         "building": "A-24",
         "pincode": 203201,
         "city": "Noida",
         "state": "UP"
      }]
}


Embedded maintains all the related data in a single document which makes it easy to recover and maintain. The entirely document can be recovered in a single query like this:


>db.users.findOne({"name":"Dilip"},{"address":1})


Guys, please note down that in the above query, db and users are the database and collection respectively.
In this process if the embedded document keeps on growing too much in size, it will impact the read/write performance.

Modeling Referenced Relationships
It is main process of designing normalized relationship. In this relationships , both the user and address documents will be maintained separately but the user document will contain a field that will reference the address document's id field.


{
   "_id":ObjectId("52mmm33cd85242f436000001"),
   "contact": "987654321",
   "dob": "01-01-1991",
   "name": "Dilip",
   "address_ids": [
      ObjectId("52ffc4a5d85242602e000054"),
      ObjectId("52ffc4a5d85242602e000456")
   ]
}


As above, the user document contains the array field address_ids which contains ObjectIds of corresponding addresses.Using these ObjectIds, we can query the address documents and get address details from there. With this approach, we will need two queries: first to fetch the address_ids fields from user document and second to fetch these addresses from address collection.



>var result = db.users.findOne({"name":"Dilip"},{"address_ids":1})
>var addresses = db.address.find({"_id":{"$in":result["address_ids"]}})

Popular posts from this blog

What is difference between UNION and UNION ALL in SQL Server

We use UNION and UNION ALL operator to combine multiple results set into one result set.
UNION operator is used to combining multiple results set into one result set but removes any duplicate rows. Basically, UNION is used to performing a DISTINCT operation across all columns in the result set. UNION operator has the extra overhead of removing duplicate rows and sorting result.
UNION ALL operator use to combine multiple results set into one result set but it does not remove any duplicate result. Actually, this does not remove duplicate rows so it is faster than the UNION operator. If you want to combine multiple results and without duplicate records then use UNION otherwise UNION ALL is better.
Following some rules for using UNION/UNION ALL operator
1.The number of the column should be the same in the query's when you want to combine them. 2.The column should be of the same data type. 3.ORDER BY clause can be applied to the overall result set not within each result set.
4.Column name of …

Dropdownlist selectedindexchanged event is not firing

<asp:DropDownList ID="ddlSource" runat="server" DataSourceID="SqlDataSource1" DataTextField="vcSuplierNm" ViewStateMode="Enabled DataValueField="vcSuplierCode" EnableViewState="true" AppendDataBoundItems="true" OnSelectedIndexChanged="ddl_OnSelectedIndexChanged" AutoPostBack="true"></asp:DropDownList>

Add property ViewStateMode="Enabled" and EnableViewState="true"
in drop DropDownList

Disable/Enable All the Foreign Key Constraint in SQL Server Database

In some scenario we need to disable all foreign key relationships from all table, suppose for bad testing purpose or you want to see what will be effect of garbage data on application or performance, due to this purpose you want to insert garbage data into table and this table contains foreign key constraints then you will get the error of foreign key constraint.
Many people face this types of issue, the following query will resolve this problem but be careful on the production server, it would be better if you do this under guidance to any DBA.
The following query will disable all constraints in the database.

execsp_msforeachtable'alter table ? nocheck constraint all'

Once you disabled all constraints you should also need to enable all constraints once you completed your work, so following query will help you to enable all constraints in the database.

execsp_msforeachtable'alter table ? with check check constraint all'

Using the above query you can resolve above described s…

Add day to ISODate in MongoDB

We can use $add operator to add days in ISODate in mongodb, $add is the Arithmetic Aggregation Operator which adds number and date in mongodb.
Syntax:

{ $add: [ <expression1>, <expression2>, ... ] }

Note:  If one of the argument is date $add operator treats to other arguments as milliseconds to add to the date.
Example: Suppose we have a Test collection as below.

{"Title" : "Add day to ISODate in MongoBD","CreatedDate" : ISODate("2016-07-07T08:00:00.000Z")}

Query to add 2 days in CreatedDate

db.Test.aggregate([      { $project: { Title: 1, AddedDate: { $add: [ "$CreatedDate", 2*24*60*60000 ] } } }    ])

Result:

{ "_id" : ObjectId("579a1567ac1b3f3732483de0"), "Title" : "Add day to ISODate in MongoBD", "AddedDate" : ISODate("2016-07-09T08:00:00.000Z") }

Note: As mentioned in above note we have to convert days in millisecond because $add operator treat to other arg…

Remove special characters from string in SQL server

I faced many times an issue to remove special characters from a string. Suppose you are working on searching concept and you have to remove the special characters from search string due to query performance, there are many solution are available but T-SQL is easily resolved this issue.
Following query may help you to resolve your issue.

DECLARE@strVARCHAR(400) DECLARE@expresVARCHAR(50)='%[~,@,#,$,%,&,*,(,),.,!]%' SET@str='(remove) ~special~ *characters. from string in sql!' WHILEPATINDEX(@expres,@str)> 0 BEGIN SET@str=Replace(REPLACE(@str,SUBSTRING(@str,PATINDEX(@expres,@str), 1 ),''),'-',' ') END SELECT@str



Query to find foreign key relationship and name of the constraints for each table in the database

Sometimes we need to find all foreign key on a table so that we can analyze the relation of a table and can find the solution accordingly. It is very difficult to see it manually, by using the following query we can find all foreign key relationships on the particular table.

SELECT K_Table=FK.TABLE_NAME, FK_Column=CU.COLUMN_NAME, PK_Table=PK.TABLE_NAME, PK_Column=PT.COLUMN_NAME, Constraint_Name=C.CONSTRAINT_NAME FROMINFORMATION_SCHEMA.REFERENTIAL_CONSTRAINTSC INNERJOININFORMATION_SCHEMA.TABLE_CONSTRAINTSFKONC.CONSTRAINT_NAME=FK.CONSTRAINT_NAME INNERJOININFORMATION_SCHEMA.TABLE_CONSTRAINTSPKONC.UNIQUE_CONSTRAINT_NAME=PK.CONSTRAINT_NAME INNERJOININFORMATION_SCHEMA.KEY_COLUMN_USAGECUONC.CONSTRAINT_NAME=CU.CONSTRAINT_NAME INNERJOIN( SELECTi1.TABLE_NAME,i2.COLUMN_NAME FROMINFORMATION_SCHEMA.TABLE_CONSTRAINTSi1 INNERJOININFORMATION_SCHEMA

How to change schema of table in SQL Server

In SQL Server 2005 and above versions  all tables grouped into schemas. When we creating a table without specify a schema SQL Server creates a default schema "dbo".  We can alter the schema of table. For example I am creating a table with default schema see bellow script.
CREATETABLE Codefari (             id INTIDENTITY(1,1),             title VARCHAR(400) ) SELECT name,SCHEMA_NAME(schema_id)as [Schema] FROMsys.tables WHERE  name ='Codefari'
Result set
name            Schema ------------------------------------------------ Codefari       dbo
(1 row(s) affected)
In result set we can see schema is dbo, if we want change schema of table then first we have to create a schema if does not exist. See below script.
CREATESCHEMA Blog GO ALTERSCHEMA Blog TRANSFER dbo.Codefari GO
SELECT name,SCHEMA_NAME(schema_id)as [Schema] FROMsys.tables WHERE  name ='Codefari'

Like in MongoDB Query

In SQL, 'LIKE' query look like as below
SELECT*FROM[dbo.][USERS]WHEREFNAMELIKE'%DILIP%'
In MongoDB it's look like as below(query in MongoDB console)
db.USERS.find({"FNAME":/DILIP/})
Same as
db.USERS.find({"FNAME":/^DILIP/})   // FNAMELIKE'DILIP%'
db.USERS.find({"FNAME":/DILIP$/})   // FNAMELIKE'%DILIP'

$regex in MongoDB