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...


Popular posts from this blog

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 EndFunction 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 Settings
Function ChangeIEZoom Dim intZoomLevel, objIE  intZoo…

QTP - Object Identification - Prerequesties

While starting a new project or proof of concept or after new QTP installation, we would face the issue in identifying objects as QTP built objects like WinList, WebEdit, etc.; instead everything will be identified as WinObject.

Here are some steps to ensure you did the environment setup RIGHT before start automating.
Did you enabled required Add-ins only while launchingDid you selected "Record >> Record and Run Settings" - This should be based on what type of application you are working with
Windows app - Windows >> Record and run test on any windows applications. Web app - Web >> Record and run test on any open browser.
Did you tried to launch UFT/QTP and then AUT.If its web, ensure browser zoom level set to 100%Try disabling the protected mode in IE for web.Launch UFT and AUT using RUN AS ADMINISTRATORAlso see the Object Identification Methods if you are interested.

Run JavaScript from QTP

Yeah, You can run your pure JavaScript from QTP using RunScript method. Lot of times, we are in need of firing events or simulating actions on web page which is not supported by QTP. At that time, you can use your direct DOM methods and directly execute your script on the web page from QTP like,
Dim MyPage, SearchBox Set MyPage = Browser("title:=Google").Page("title:=Google") Set SearchBox = MyPage.RunScript("document.getElementsByName('q')(0);") SearchBox.Value="testing"
'if objects available in frames, Set SearchBox = MyPage.RunScript("document.frames(4).document.getElementsByName('q')(0);")
Set objFrame = Browser("title:=Google").Page("title:=Google").Frame("title:=something")
objFrame.RunScript("document.getElementsByName('q')(0);") Also, you can execute by obtaining actual browser window object if you have IE app like, Dim IEApp Set IEApp = CreateObject("Internet…