Encrypting an existing sqlite database in sqlcipher

I am using sql cipher in Qt and i want to encrypt an existing sqlite database.On the Api docs here: http://sqlcipher.net/sqlcipher-api#attach this is how to do it:

Code:

---

ATTACH DATABASE 'encrypted.db' AS encrypted KEY 'secret'; -- create a new encrypted database
CREATE TABLE encrypted.t1(a,b); -- recreate the schema in the new database (you can inspect all objects using SELECT * FROM sqlite_master)
INSERT INTO encrypted.t1 SELECT * FROM t1; -- copy data from the existing tables to the new tables in the encrypted database
DETACH DATABASE encrypted;

---

The following two line confuse me:

CREATE TABLE encrypted.t1(a,b);

and

INSERT INTO encrypted.t1 SELECT * FROM t1;

What does (a,b) mean and why is it used in the first statement and not in the second?.

Thanks.

---

Added after 1 40 minutes:

Someone has suggested to me that the a,b could be table columns.I am looking into that.

"(a, b)" is the columns. Since the original t1, and the encrypted.t1 have an identical schema then "select * from t1" will produce columns in exactly the same order as in the definition of encrypted.t1 so a column list is not required.

Hello Chris,thanks.I have the sql cipher driver working fine but i cannot create an encrypted database yet.Lets put aside the attach database method for a moment.What other method is there to make an encrypted database?.

Code:

---

QSqlDatabase db = QSqlDatabase::addDatabase("QSQLCIPHER");
db.setDatabaseName(/*add the database path here*/);
if (!db.open()) 
  qFatal("Could not access database.");
QSqlQuery query(db);
query.exec("PRAGMA key = 'secretkey';");

---

In this example http://www.qtcentre.org/wiki/index.p...yption_support there is no mention of creating an encrypted database i have noted.

That looks good to me. What is the problem? The new database will be zero bytes until you actually define some tables in it.

I will try keying the database using the command shell and creating some tables and i will report back what i get.The problem i had is that the database wasn't being encrypted.

I have re-evaluated my applications needs and have resolved to put aside the sqlite encryption and to obscure only parts that are of paramount importance such as start of trial dates etc.
The driver sql cipher i believe is still very good and i shall resume from where i left off in the future but as of now i have another solution which works just fine.

@Chris tried keying the database from the sqlite windows shell but the database is not being encrypted.I have decided to try some other day since i have lots of class work to do.

Thanks.

Attachment 7021