Reply to thread

Message

[QUOTE="Kevin McMurtrie, post: 5050688"]
What is your database key?

If it's 1, 2, 3, 4, ... then encrypting it will simply reveal your
encryption key. If characters aren't efficient for your keys, simply use
a translation table between the random and sequential values.  Use the
randomized value as a database key on all traffic leaving and entering
your server.  It prevents the public from guessing new database keys.

create table urlparams
{
param char(16) primary key,
id integer unique not null references main_table (id)
}
-- param is the outside database key made of random characters
-- id is the local primary key

create table main_table
{
id integer primary key,
...
}

create table other_table
{
id integer primary key references main_table (id),
...
}

create table more_table
{
id integer primary key references main_table (id),
...
}

You fetch all your table data together efficiently in one join:

select ... from main_table, other_table, more_table, urlparams
where
urlparams.param=?
and urlparams.id=main_table.id
and urlparams.id=other_table.id
and urlparams.id=more_table.id
[/QUOTE]

Verification