I'm using sqlite.

I need a DB that contains:
- a set of general tables
- a variable number of sets of users tables.

The first set is accessed by every-one.
Each of the users' set 'is identical in structure to the others,
but it is specific in content respect to the owner.

I can manage authentication through my application.
What I don't know how to do in a suitable way is the design of a group
of identical tables repeated for each user.

Could anyone help?
Thanks

Ciao, Licia.

ilochab wrote:

You don't. Any design that encodes data in table names that is readily
encoded in the values of the tables is a poor design.

For each set of identical tables, use a single table and use restrict to
limit what data individual users can manipulate.

ilochab wrote:

You don't. Any design that encodes data in table names that is readily
encoded in the values of the tables is a poor design.

For each set of identical tables, use a single table and use restrict to
limit what data individual users can manipulate.

ilochab wrote:

You don't. Any design that encodes data in table names that is readily
encoded in the values of the tables is a poor design.

For each set of identical tables, use a single table and use restrict to
limit what data individual users can manipulate.

ilochab wrote:

You don't. Any design that encodes data in table names that is readily
encoded in the values of the tables is a poor design.

For each set of identical tables, use a single table and use restrict to
limit what data individual users can manipulate.

ilochab wrote:

You don't. Any design that encodes data in table names that is readily
encoded in the values of the tables is a poor design.

For each set of identical tables, use a single table and use restrict to
limit what data individual users can manipulate.

ilochab wrote:

You don't. Any design that encodes data in table names that is readily
encoded in the values of the tables is a poor design.

For each set of identical tables, use a single table and use restrict to
limit what data individual users can manipulate.

ilochab wrote:

You don't. Any design that encodes data in table names that is readily
encoded in the values of the tables is a poor design.

For each set of identical tables, use a single table and use restrict to
limit what data individual users can manipulate.

ilochab wrote:

You don't. Any design that encodes data in table names that is readily
encoded in the values of the tables is a poor design.

For each set of identical tables, use a single table and use restrict to
limit what data individual users can manipulate.

ilochab wrote:

You don't. Any design that encodes data in table names that is readily
encoded in the values of the tables is a poor design.

For each set of identical tables, use a single table and use restrict to
limit what data individual users can manipulate.