Multi user web application and mySql and cgi

Hi,

Just now I am working on a project to develop a web application for
multiple users.
I thought of two different types of tables:

1. user table: with the user-specific data in it (name, passwrd...)
2. data table: Every user should have it's own data-table within the
dadabase. The user data-tables are of the same structure, they have the
same columns, respectively. The User should then fill in their data from
a quality survey (all the users do the same survey). Sorry if this
wasn't posted clear enough by me.


I thought doining the scripts with cgi/perl and the databases with mySQL.

My Question: Is it principially ok doing it this way?
Of course security questions about logging in and how to direct every
user to his own table is what i've not thought about jet, it's more a
principle question if it's tecnically feasible this way.

Best greets from Austria
Tom

Ps.: Answers in german are ok.

Re: Multi user web application and mySql and cgi

Andreas
--
q: why do so many people take an instant dislike to mysql?
a: it saves time (oicu in #postgresql)
Explaining the concept of referential integrity to a mysql user is like
explaining condoms to a catholic (Shadda in #postgresql)

Re: Multi user web application and mySql and cgi

Danke Andreas,

Mittlerweile ist mir das auch klar geworden.
Ich hätte noch eine Frage. Ist es prinzipiell emphehlenswert die
kommunikation user und datenbank über cgi zu machen?
Ist es mit cgi möglich alles möglichst sicher zu gestalten, oder besser
php verwenden?

Thomas


Andreas Kretschmer schrieb:
> begin Thomas W. wrote:
>
>>1. user table: with the user-specific data in it (name, passwrd...)
>>2. data table: Every user should have it's own data-table within the
>>dadabase. The user data-tables are of the same structure, they have the
>>same columns, respectively. The User should then fill in their data from
>>a quality survey (all the users do the same survey). Sorry if this
>>wasn't posted clear enough by me.
>
>
>
>>I thought doining the scripts with cgi/perl and the databases with mySQL.
>
>
>>My Question: Is it principially ok doing it this way?
>>Of course security questions about logging in and how to direct every
>>user to his own table is what i've not thought about jet, it's more a
>>principle question if it's tecnically feasible this way.
>
>
>
>>Ps.: Answers in german are ok.
>
>
> Dein 'Konzept' widerspricht dem Konzept einer rel. Datenbank. Du hast
> dann für N User auch N Tabellen. Eine Änderung (neue Spalte) hast Du
> dann auf allen N Tabellen zu machen. Eine Abfrage über die
> Umfrageresultate z.B. aller User wird schwer etc. (Durchschnitt der
> Ergebnisse etc.)
> Der normale Weg wäre, in der 'data table' eine Spalte mit einer
> Reference auf die UserID in der 'user table' zu machen und fertig.
>
>
>
> end
> Andreas

Re: Multi user web application and mySql and cgi

Andreas
--
q: why do so many people take an instant dislike to mysql?
a: it saves time (oicu in #postgresql)
Explaining the concept of referential integrity to a mysql user is like
explaining condoms to a catholic (Shadda in #postgresql)

Re: Multi user web application and mySql and cgi

Andreas
--
q: why do so many people take an instant dislike to mysql?
a: it saves time (oicu in #postgresql)
Explaining the concept of referential integrity to a mysql user is like
explaining condoms to a catholic (Shadda in #postgresql)