Namespaces

Variants
Actions

Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries over the next few weeks. Thanks for all your past and future contributions.

Archived:Using SQL API for creating non-secure and secure databases on Symbian

From Wiki
Jump to: navigation, search

Archived.pngArchived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

Article Metadata
Tested with
Devices(s): Nokia 6220 Classic
Compatibility
Platform(s): S60 3rd Edition, FP2
S60 3rd Edition FP2
Article
Keywords: RSqlDatabase, TSecurityPolicy, RSqlSecurityPolicy,RSqlDatabase::Create(), RSqlDatabase::Exec(), RSqlDatabase::Close(), RSqlSecurityPolicy::Create(), RSqlDatabase::Copy(),RSqlDatabase::Delete(), RSqlSecurityPolicy::SetDbPolicy(), RSqlSecurityPolicy::SetPolicy()
Created: aknyman (24 Apr 2008)
Last edited: lpvalente (20 Aug 2012)

Contents

Overview

This code snippet shows how the SQL API's RSqlDatabase handle class allows the user to interact with the SQL server and create either a non-secure or secure database. Non-secure databases are databases that can be accessed and updated by any program. Secure databases have a defined static policy and can be accessed only by authorized clients with specific capabilities. To create a secure database, the UID of the application that creates the database and security policy are needed.

Another possibility to create a new database is to make a copy of an existing database with the method RSqlDatabase::Copy(). Databases can be deleted using the method RSqlDatabase::Delete().

This snippet can be self-signed.

MMP file

The following libraries are required:

LIBRARY euser.lib
LIBRARY sqldb.lib


The following capabilities are needed to test the secure database in this example:

CAPABILITY ReadUserData
CAPABILITY WriteUserData


Source file

#include <e32base.h>
#include <SqlDb.h>
 
void CreateDatabasesL()
{
//== Create non-secure database ==
RSqlDatabase database;
 
_LIT(KNonSecureDbName, "\\nonsecure.db");
TInt error = database.Create(KNonSecureDbName);
 
if(error == KErrNone)
{
CleanupClosePushL(database);
 
//Create MOVIES table
_LIT(KSqlCreateTableMovies, "CREATE TABLE MOVIES(ID INTEGER, TITLE TEXT,
YEAR SMALLINT, DURATION SMALLINT, COLOR BOOLEAN)"
);
User::LeaveIfError(database.Exec(KSqlCreateTableMovies));
 
_LIT(KSqlCreateTableMoviesIndex, "CREATE UNIQUE INDEX IDX ON MOVIES (ID)");
User::LeaveIfError(database.Exec(KSqlCreateTableMoviesIndex));
 
//Insert data into MOVIES table
_LIT(KSqlInsertIntoTableMovies, "INSERT INTO MOVIES(ID, TITLE, YEAR,
DURATION, COLOR) VALUES(1, 'numberOne', 1999, 120, 'true')"
);
User::LeaveIfError(database.Exec(KSqlInsertIntoTableMovies));
 
CleanupStack::PopAndDestroy(); //database
}
else
{
//creating database failed:
//reason could be e.g. already exists, the disk full, bad database name...
}
 
//== Create secure database ==
 
TSecurityPolicy defaultPolicy;
RSqlSecurityPolicy securityPolicy;
 
// Create security policies container object using a default security policy.
securityPolicy.Create(defaultPolicy);
CleanupClosePushL(securityPolicy);
 
// Set up policy to apply to database schema and assign it
TSecurityPolicy schemaPolicy(ECapabilityReadUserData, ECapabilityWriteUserData);
User::LeaveIfError(securityPolicy.SetDbPolicy(RSqlSecurityPolicy::ESchemaPolicy,
schemaPolicy));
 
// Set up policy to apply to write activity on the database and assign it
TSecurityPolicy readPolicy(ECapabilityReadUserData);
User::LeaveIfError(securityPolicy.SetDbPolicy(RSqlSecurityPolicy::EReadPolicy, readPolicy));
 
// Set up policy to apply to write activity to the database table named
// "MOVIES" and assign it
TSecurityPolicy tablePolicy(ECapabilityWriteUserData);
 
_LIT(KMoviesTableName, "MOVIES");
User::LeaveIfError(securityPolicy.SetPolicy(RSqlSecurityPolicy::ETable, KMoviesTableName,
RSqlSecurityPolicy::EWritePolicy, tablePolicy));
 
// Create the database, passing the security policies
_LIT(KSecureDbName, "[E80000AF]secure.db"); //Note: [UID3]
error = database.Create(KSecureDbName, securityPolicy);
 
//close RSqlSecurityPolicy object.
CleanupStack::PopAndDestroy(); //securityPolicy
 
if(error == KErrNone)
{
CleanupClosePushL(database);
//Create BOOKS table
_LIT(KSqlCreateTableBooks, "CREATE TABLE BOOKS(ID INTEGER NOT NULL,
TITLE TEXT, AUTHOR TEXT)"
);
User::LeaveIfError(database.Exec(KSqlCreateTableBooks));
 
//insert data
_LIT(KSqlInsertIntoTableBooks, "INSERT INTO BOOKS(ID, TITLE, AUTHOR)
VALUES(1, 'numberOne', 'author1')"
);
User::LeaveIfError(database.Exec(KSqlInsertIntoTableBooks));
 
CleanupStack::PopAndDestroy(1); //database
}
else
{
//database creation failed:
//reason could be e.g. already exists, the disk full, bad database name...
}
 
}

Postconditions

Two databases, nonsecure.db and secure.db, have been created and the example rows are inserted into the databases.

nonsecure.db after creation:

TABLE:MOVIES
ID|TITLE |YEAR|DURATION|COLOR
1 |numberOne|1999|120 |true

[UID3]secure.db after creation:

TABLE:BOOKS
ID|TITLE |AUTHOR
1 |numberOne|author1

See also

This page was last modified on 20 August 2012, at 17:33.
77 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.

 

Thank you!

We appreciate your feedback.

×