General discussion

Locked

related to Database planning

By Arati ·
Hello All

I am developing a site which will take data from our members. This data will first go to the administrator through VB application.
After validation of this data administrator will send this data to final database, Which will used in our site.

Now I want to perpare database for above.

can u suggest me the best practical method to design database for this type of site.

I think I have to prepare 2 database with same table in it.
1) when the data is inputed from site by our
member.
2) Database for the data which is transfered by
administrator, Which will be used in site for
final user.
we use SQL as backhand.

thanks
arati

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

related to Database planning

by Bob Sellman In reply to related to Database plann ...

I would suggest one database with two versions of the table. One version would be for user input, the second would be the accepted data. The user input table could contain one or more columns to contain data that verifies when the administrator validated the data. The accepted data table would contain those same columns, but with the important difference that they cannot be null.

Using one database would enable you to use any lookup and reference tables to verify user input and minimize input errors. Your users would not have access to the accepted data table except for reporting and data analysis access, in which case they could not input or modify data in the accepted data table. The administrator would be the only person who could access the validation column(s) in the user input table and who could then transfer validated rows from the user input table to the accepted data table.

You could also restrict the user input access to only those records in the user input table where the validated columns were null. This would prevent users from modifying data that had been validated by the administrator, but not yet moved to the accepted data table.

Collapse -

related to Database planning

by Arati In reply to related to Database plann ...

Poster rated this answer

Collapse -

related to Database planning

by timfox In reply to related to Database plann ...

Having two tables that will be of the same design may cause too many headaches (namely duplication of data, ensuring records are correctly deleted from one table before after the record is copied to the next table, providing lookup tables etc). Why not provide a flag field 'AdminApproved' or 'AdminChecked', which is defaulted to false for new records and only updated if the Administrator approves the record. Then there is no data transafer required - just different views of the same table. ie. The Amdministrator can see all records (approved and awaiting approval), other staff can only see the approved (AdminApproved=TRUE) records.

Collapse -

related to Database planning

by Arati In reply to related to Database plann ...

Poster rated this answer

Collapse -

related to Database planning

by Arati In reply to related to Database plann ...

This question was closed by the author

Back to Web Development Forum
5 total posts (Page 1 of 1)  

Related Forums