Skip to main content

RDBMS - A QuickView of Concepts


Relational DataBases:
4 major concepts.
1. keys
2. Relationships
3. Normal Forms i.e. Normalization
4. Integrity rules


>> Keys and Uniqueness
>> Primary Keys
-- Every row in table is unique
-- To achieve this, Primary Key
-- 2 types; Single and Composite
-- Simple -- Only one column will have unique value - Primary key
-- Composite - Combination of more than 1 column will have unique value - These columns are called as candidate keys; Main one is primary key; Others are alternate keys;
>> Foreign Keys
-- Column to be referred from related table to find matched row from a table which have a primary key.


>> Relationships
>> One to One
-- Every record in 1st table must have at most 1 record in 2nd table.
-- Also every record in 2nd table must have atmost 1 record in 1st table.
>> One to many
-- Every record in 1st table will have any number of records(0, 1 or higher) in 2nd table.
-- But every record in 2nd table will have atmost 1 record in 1st table.
>> Many to many
-- Every record in 1st table will have any number of records(0, 1 or higher) in 2nd table.
-- Also every record in 2nd table will have any number of records(0, 1 or higher) in 1st table.
-- Normally designed using multiple One to Many like Customer --> Orders --> OrderPaymentType
-- Every customer will have many orders. Also every OrderPayementType will be used for many Orders.
-- So, Many to Many relationship.


>> Normal Forms
>> 1NF
-- Every column for any row should be atomic. ie. should contain one value not list of values or array of values
-- Should not have repeating groups of columns
>> 2NF
-- 1NF + Non-key columns should be dependent on entire primary key (whatever single or combosite)
-- Should be able to get values of non-key columns when I know entire key columns values not by knowing any key column value.
>> 3NF
-- 2NF + Non-key columns should be independent each other.
>> Boyce/Codd NF
-- Same as 3NF. (Non-key columns should be functionally independent each other)
>> 4NF
>> 5NF


>> Integrity Rules
>> General Rules
>> Entity Integrity
-- Entire Primary key columns should not be null.
>> Referential Integrity
-- Should not allow to add record in 2nd table(Orders) without having record in 1st table(Customers)
-- Should not allow to orphan the record in 2nd table when I deleted/updated the record in 1st table. 3 ways to restrict.
1. DisAllow - Should not allow to delete record in 1st table if referred records there in 2nd table.
2. Cascade - Should delete/update the referred records also. ie. both tables should affect.
3. Nullify - Set null to foreign keys in 2nd table.
>> DataBase Specific Rules or Business Rules
-- Applicable only for particular database.
-- Used to avaoid wrong entries and garbages.
-- Like, CustomerOrderDate should be between Today's date to 10 days.
-- Like validation rules for field values.


Hope this will give some quick view of Relational DataBase Management systems...

Comments

Popular posts from this blog

Some good Resources / Blogs / Sites for Selenium Users

Here I have listed out some good blogs and sites by extensive selenium automation users. Hope these will help you a lot. http://automationtricks.blogspot.com  - by NirajKumar http://www.theautomatedtester.co.uk/ http://testerinyou.blogspot.com   - by Naga/Mathu http://seleniumready.blogspot.com  - by Farheen Khan http://seleniumdeal.blogspot.com/  - Amit Vibhuti http://seleniumexamples.com/blog Sauce Labs and BrowserMob are companies doing cloud and extensive selenium automation services, products, etc http://saucelabs.com/blog http://blog.browsermob.com http://testingbot.com/ Cedric Beust -  creator of the TestNG Java testing framework. http://beust.com/weblog/ http://blog.reallysimplethoughts.com/  - by Samit Badle, Created many Selenium IDE Plug-Ins Available Colud Testing: 1. SauceLabs 2. Soasta 3. BrowserMob 4. CloudTesting.com  etc. Selenium Testing Products: 1. Twist by ThoughtWorks 2.  TestMaker by  PushToTest 3. Element34 company providi

UFT - Take full page screenshot by scrolling the page

'######################################################################################## 'This is navigate through the full page and taking individual screenshot of visible area '######################################################################################## Function TakeScreenshot Dim intScrolls, intScroll, strScrollPos Set pgApp = Browser ( " " ) .Page ( " " ) intScrolls = Round ( pgApp . RunScript ( " document.documentElement.scrollHeight / (screen.height) " ) , 2 ) If intScrolls < 1 Then intScrolls = - 1 pgApp . RunScript " window.scrollTo(0, 0); " Wait 1 Browser ( " " ) .CaptureBitmap " C:\screenshot0.png " , True For intScroll = 0 To intScrolls If Environment . Value ( " Browser " ) = " CHROME " Then strScrollPos = " scrollY " Else strScrollPos = " document.documentElement.scrollTop " End If If p

Change IE Browser ZOOM settings

Lot of UI automation testers could have faced this problem as we could change the zoom settings while operating manually for our convenience and forgot to reset to 100%. But our QTP and some other related tools would operate the browser perfectly if browser zoom is 100%. So wee need to change the zoom before start to run the scripts. Its better to have a code snippet in our framework to change this zoom setting right? Here we go... 1. We can simply change the Registry values before Invoking IE Function  ChangeRegistry   Dim  objShell   Set  objShell =  CreateObject ( "WScript.Shell" )  objShell.RegWrite  "HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Zoom\ZoomFactor" ,  "100000" ,  "REG_DWORD"   Set  objShell =  Nothing End   Function This option is very useful. But in real time, lot of customers could have restricted write access to windows registry. So we can try other options. 2. Use IE COM object and Change