Re: A philosophical newbie issue: catch redundant errors via relationships or programmically?
Date: Sun, 30 Dec 2007 16:40:38 +0100
Just some nits:
> ... Now I want to extend this
> architecture of tables
'schema' is the word you were looking for.
> Everything worked fine for this CD extension, I set in up in no time,
> but I noticed that when a user enters data, sometimes the same
> combination of Bank Account number and CD identifier (CD ID) will be
> entered by mistake, which under the below architecture will create a
> new record. I don't want this.
This means you want to constrain your data.
> I have various ideas on how to fix this programmically (such as a
> simple lookup table so when the combination of particular Bank Account
> and CD ID are found, a warning box will tell the user that this record
> already exists).
Good to warn your users they are about to violate a constraint, not good to guard your data in a UI.
Why this tbl prefix? Should I call you guyRay?Received on Sun Dec 30 2007 - 16:40:38 CET