Curious

Hi all,
I just wish to know Few things
Is there any way we can block the data manipulation from Back End?
(
As I have an application which has senstive data Any changes from
back end can cause problem
) So I have two choices block entry from back end or thoroughly check
in the processes using data but data can be incorrect as it is entered
from back end.
While designing database(s) what Should be considered like "The
application depends on data" or " Data depends upon Application"
Any Thoughts
With Warm regards
Jatinder Singh> ) So I have two choices block entry from back end or thoroughly check
> in the processes using data but data can be incorrect as it is entered
> from back end.
Constraints prevent garbage from being stored in a database. A user can
enter an incorrect value if and only if it passes all of the validations in
the application and the constraints on the database. Nothing can prevent
that. If data cannot be entered incorrectly through the front end but can
through the back end, then your database definition is incomplete--that is,
one or more constraints is absent.
Validation should occur in both the application and the database. A
database can be accessed by more than one application, so the same exact
validation code must exist in every application. Placing a constraint on
the database forces the application developer to write code either to
validate the data before submitting it, or to handle the constraint
violation afterwards. In either case, it keeps the garbage out of the
database. It also helps to prevent the introduction of garbage by the
resident loose-cannon with access to query analyzer.
Nothing kills a project schedule faster than assuming that data in an
existing database is consistent and correct. If you look at a database
schema and find few if any constraints, then you can be 99.44% sure that the
database contains garbage, so you must build time and money into the project
to fix it, or you'll find yourself working for free. Leaving the garbage is
not an option, because management will always point the finger at the last
person who touched it. In addition, your application will need additional
code to cope with the garbage.
Once you know what information you need to store in the database, the entire
focus of database design changes to keeping garbage out. Eliminating
redundancy through normalization eliminates update anomalies which serves to
keep garbage out. Adding foreign key constraints prevents orphaned
information, which is also garbage. Adding check constraints ensures that
data being entered into a column or row meet minimum validity
requirements--also preventing the introduction of garbage.
"jsfromynr" <jatinder.singh@.clovertechnologies.com> wrote in message
news:1124260202.310593.32240@.f14g2000cwb.googlegroups.com...
> Hi all,
> I just wish to know Few things
> Is there any way we can block the data manipulation from Back End?
> (
> As I have an application which has senstive data Any changes from
> back end can cause problem
> ) So I have two choices block entry from back end or thoroughly check
> in the processes using data but data can be incorrect as it is entered
> from back end.
> While designing database(s) what Should be considered like "The
> application depends on data" or " Data depends upon Application"
> Any Thoughts
> With Warm regards
> Jatinder Singh
>|||Thanks Brian
For correcting my Mistake and guiding me with thorough Explaination
Wiath Warm regards
Jatinder Singh