Privacy Policy

Effective date: March 08, 2019
PLSQL ("us", "we", or "our") operates the mobile application (the "Service").
This page informs you of our policies regarding the collection, use, and disclosure of personal data when you use our Service and the choices you have associated with that data. Our Privacy Policy for PLSQL is created with the help of the Free Privacy Policy website.
We use your data to provide and improve the Service. By using the Service, you agree to the collection and use of information in accordance with this policy. Unless otherwise defined in this Privacy Policy, terms used in this Privacy Policy have the same meanings as in our Terms and Conditions.

Information Collection And Use

We collect several different types of information for various purposes to provide and improve our Service to you.

Types of Data Collected

Personal Data

While using our Service, we may ask you to provide us with certain personally identifiable information that can be used to contact or identify you ("Personal Data"). Personally identifiable information may include, but is not limited to:

• Cookies and Usage Data

Usage Data

When you access the Service by or through a mobile device, we may collect certain information automatically, including, but not limited to, the type of mobile device you use, your mobile device unique ID, the IP address of your mobile device, your mobile operating system, the type of mobile Internet browser you use, unique device identifiers and other diagnostic data ("Usage Data").

Tracking & Cookies Data

We use cookies and similar tracking technologies to track the activity on our Service and hold certain information.
Cookies are files with small amount of data which may include an anonymous unique identifier. Cookies are sent to your browser from a website and stored on your device. Tracking technologies also used are beacons, tags, and scripts to collect and track information and to improve and analyze our Service.
You can instruct your browser to refuse all cookies or to indicate when a cookie is being sent. However, if you do not accept cookies, you may not be able to use some portions of our Service.
Examples of Cookies we use:

• Session Cookies. We use Session Cookies to operate our Service.
• Preference Cookies. We use Preference Cookies to remember your preferences and various settings.
• Security Cookies. We use Security Cookies for security purposes.

Use of Data

PLSQL uses the collected data for various purposes:

• To provide and maintain the Service
• To notify you about changes to our Service
• To allow you to participate in interactive features of our Service when you choose to do so
• To provide customer care and support
• To provide analysis or valuable information so that we can improve the Service
• To monitor the usage of the Service
• To detect, prevent and address technical issues

Transfer Of Data

Your information, including Personal Data, may be transferred to — and maintained on — computers located outside of your state, province, country or other governmental jurisdiction where the data protection laws may differ than those from your jurisdiction.
If you are located outside India and choose to provide information to us, please note that we transfer the data, including Personal Data, to India and process it there.
Your consent to this Privacy Policy followed by your submission of such information represents your agreement to that transfer.
PLSQL will take all steps reasonably necessary to ensure that your data is treated securely and in accordance with this Privacy Policy and no transfer of your Personal Data will take place to an organization or a country unless there are adequate controls in place including the security of your data and other personal information.

Disclosure Of Data

Legal Requirements

PLSQL may disclose your Personal Data in the good faith belief that such action is necessary to:

• To comply with a legal obligation
• To protect and defend the rights or property of PLSQL
• To prevent or investigate possible wrongdoing in connection with the Service
• To protect the personal safety of users of the Service or the public
• To protect against legal liability

Security Of Data

The security of your data is important to us, but remember that no method of transmission over the Internet, or method of electronic storage is 100% secure. While we strive to use commercially acceptable means to protect your Personal Data, we cannot guarantee its absolute security.

Service Providers

We may employ third party companies and individuals to facilitate our Service ("Service Providers"), to provide the Service on our behalf, to perform Service-related services or to assist us in analyzing how our Service is used.
These third parties have access to your Personal Data only to perform these tasks on our behalf and are obligated not to disclose or use it for any other purpose.

Links To Other Sites

Our Service may contain links to other sites that are not operated by us. If you click on a third party link, you will be directed to that third party's site. We strongly advise you to review the Privacy Policy of every site you visit.
We have no control over and assume no responsibility for the content, privacy policies or practices of any third party sites or services.

Children's Privacy

Our Service does not address anyone under the age of 18 ("Children").
We do not knowingly collect personally identifiable information from anyone under the age of 18. If you are a parent or guardian and you are aware that your Children has provided us with Personal Data, please contact us. If we become aware that we have collected Personal Data from children without verification of parental consent, we take steps to remove that information from our servers.

Changes To This Privacy Policy

We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page.
We will let you know via email and/or a prominent notice on our Service, prior to the change becoming effective and update the "effective date" at the top of this Privacy Policy.
You are advised to review this Privacy Policy periodically for any changes. Changes to this Privacy Policy are effective when they are posted on this page.

Contact Us

If you have any questions about this Privacy Policy, please contact us:

• By email: paragshukla007@gmail.com

Difference Between System Level Privileges and Objects Level Privileges

System Privileges	Table Level Privileges (Object Level)
System Privileges are normally granted by a DBA to users.	Object privileges means privileges on objects such as tables, views, synonyms, procedure. These are granted by owner of the object.
This privileges allows a user to manage database and server.	This privileges allows a user to perform certain action upon certain database objects
List of privileges ·         CREATE USER ·         CREATE TABLE ·         CREATE SESSION	List of privileges ·         SELECT ·         INSERT,UPDATE,DELETE ·         EXECUTE
To get information about system level privileges ·         SELECT * FROM USER_SYS_PRIVS ·         SELECT * FROM ROLE_SYS_PRIVS	To get information about object level privileges ·         SELECT OWNER,TABLE_NAME,PRIVILEGE FROM USER_TAB_PRIVS ·         SELECT * FROM ROLE_TAB_PRIVS
Syntax GRANT privileges TO username;	Syntax GRANT privileges ON object TO username;
Example GRANT CREATE SESSION, CREATE PROCEDURE TO PARAG;	Example GRANT SELECT, INSERT ON EMPLOYEE TO PARAG;

SYSTEM LEVEL PRIVILEGES AND OBJECTS LEVEL PRIVILEGES

SQL Query to recover dropped tables.

Is it possible to recover the dropped tables?

Yes, We can recover the dropped tables using flashback query if it is not permanently deleted.

Whenever you execute any dropped table query, dropped table information are stored in recyclebin. You can execute show recyclebin, it will display objects in recyclebin.

Example

SQL> CREATE TABLE TEST(ID INT);

Table created.

SQL> INSERT INTO TEST VALUES(1001);

1 row created.

SQL> INSERT INTO TEST VALUES(1002);

1 row created.

SQL> INSERT INTO TEST VALUES(1003);

1 row created.

SQL> INSERT INTO TEST VALUES(1004);

1 row created.

SQL> COMMIT;

Commit complete.

SQL> DROP TABLE TEST;

Table dropped.

SQL> SHOW RECYCLEBIN
ORIGINAL NAME    RECYCLEBIN NAME                OBJECT TYPE  DROP TIME
---------------- ------------------------------ ------------ -------------------
TEST             BIN$Q2h8H7dpTPa/+/wsarPBgA==$0 TABLE        2016-08-13:15:08:34

SQL> FLASHBACK TABLE TEST TO BEFORE DROP;

Flashback complete.

SQL> SELECT * FROM TEST;

        ID
----------
      1001
      1002
      1003
      1004


We can also clear all the object from recyclebin using purge command.

Example

SQL> DROP TABLE TEST;

Table dropped.

SQL> SHOW RECYCLEBIN
ORIGINAL NAME    RECYCLEBIN NAME                OBJECT TYPE  DROP TIME
---------------- ------------------------------ ------------ -------------------
TEST             BIN$WztpWgD2TOCdtIxsAv+CSw==$0 TABLE        2016-08-13:15:14:53

SQL> PURGE RECYCLEBIN;

Recyclebin purged.


SQL> SHOW RECYCLEBIN

We can also recover dropped table with new name.

Example

SQL> DROP TABLE TEST;

Table dropped.

SQL> SELECT * FROM NEWTEST;
SELECT * FROM NEWTEST
              *
ERROR at line 1:
ORA-00942: table or view does not exist


SQL> FLASHBACK TABLE TEST TO BEFORE DROP
  2     RENAME TO NEWTEST;

Flashback complete.

SQL> SELECT * FROM NEWTEST;

        ID
----------
      1001
      1002
      1003

      1004

SQL query for hierarchical retrieval of employees working in any organization.

To evaluates hierarchical query oracle provides PRIOR expression of CONNECT BY condition.

Example

CREATE TABLE employees 
  ( 
     empid       INT PRIMARY KEY, 
     ename       VARCHAR2(30) NOT NULL, 
     designation VARCHAR2(20), 
     parent_id   INT 
  );


SELECT * FROM EMPLOYEES;

     EMPID ENAME                          DESIGNATION           PARENT_ID
---------- ------------------------------ -------------------- ----------
         1 P.P.TYAG VALLABH SWAMIJI       SECRETARY
         2 Dr.J.N.Shah                    DIRECTOR                      1
         3 Dr.G.D.Acharya                 PRINCIPAL                     2
         4 Dr.S.R.VARMA                   PRINCIPAL                     2
         5 Dr.K.R.VADALIYA                PRINCIPAL                     2
         6 Dr.G.C.JOSHI                   PRINCIPAL                     2
         7 Dr.A.U.PATEL                   PRINCIPAL                     2
         8 Dr.NISHANT VACHHANI            HOD                           4
         9 Dr.ASHISH KOTHARI              HOD                           3
        10 PROF.J.N.RATHOD                HOD                           3
        11 PROF.P.C.SHUKLA                HOD                           4
        12 DR.STAVAN PATEL                HOD                           7
        13 PROF.ANKIT FALDU               ASSISTANT PROFESSOR          11
        14 DR.PRATIK VANZARA              ASSISTANT PROFESSOR          12
        15 PROF.VIVEK VYAS                ASSISTANT PROFESSOR          11
        16 PROF.KALPESH POPAT             ASSISTANT PROFESSOR          11
        17 PROF.PRAKASH GUJARATI          ASSISTANT PROFESSOR          12
        18 PROF.DIVYESH GOHEL             ASSISTANT PROFESSOR          12
        19 DR.AMIT RAJDEV                 ASSISTANT PROFESSOR           8
        20 PROF.ANKIT GANDHI              ASSISTANT PROFESSOR           8


20 rows selected.

SELECT Sys_connect_by_path(ename, '-') "Path" 
FROM   employees 
START WITH Upper(ename) = 'P.P.TYAG VALLABH SWAMIJI' 
CONNECT BY PRIOR empid = parent_id 

SELECT ename, designation, LEVEL 
FROM   employees 
START WITH Upper(ename) = 'P.P.TYAG VALLABH SWAMIJI' 
CONNECT BY PRIOR empid = parent_id