IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New Stateful.
Desktop applications.
Regards,

-scott anderson

"Welcome to Rivendell, Mr. Anderson..."
New Then the issue is multi-column constraints
Like I said, if changing the first column will cause it to be in violation of a constraint until the second (third, fourth, etc) columns are also changed, you can't commit the update until all columns are changed.

ie: Loan amount has to be lower that purchase amount. If you want to raise both values you have to raise the purchase amount first. This case can be handled easily by simply warning the user and making them change the other field first. But what about a case where you actually need to update two fields in the same transaction to maintain referential integrity?

This is only a problem in a situation with multi-column constraints, but I would avoid it anyway. Business rules can change, and constraints can be added to tables after the UI is built.
===

Implicitly condoning stupidity since 2001.
     Discussion topic: data-aware controls on forms - (admin) - (31)
         How active? Context? - (ben_tilly) - (3)
             Re: How active? Context? - (admin) - (2)
                 Are you really asking why Access is a bad idea? -NT - (ben_tilly) - (1)
                     Whoops. - (admin)
         Bad idea. - (mmoffitt) - (18)
             Implementation vs effect - (ben_tilly) - (17)
                 Consider what goes on in most such setups. - (mmoffitt) - (12)
                     Don't be sure about the surely - (ben_tilly) - (11)
                         Re: Don't be sure about the surely - (admin) - (4)
                             That I agree with - (ben_tilly) - (3)
                                 Why more? - (admin) - (2)
                                     Duplication of information - (ben_tilly) - (1)
                                         Must depend on what you're doing. - (admin)
                         I can't add much to what Scott said. - (mmoffitt) - (5)
                             Then see my response to Scott - (ben_tilly) - (4)
                                 I did. And how? - (mmoffitt) - (3)
                                     Ah, good point - (ben_tilly) - (2)
                                         Problem is rollback - (drewk) - (1)
                                             That's only an argument for a wrapper - (ben_tilly)
                 Er, what headaches? - (admin) - (3)
                     Depends how you're set up - (ben_tilly) - (2)
                         Re: Depends how you're set up - (admin) - (1)
                             More moving parts - (ben_tilly)
         always thought that all forms should be a view of the table - (boxley)
         Depends on the kind of data - (ChrisR) - (2)
             Mostly agree - (ben_tilly) - (1)
                 Love 'impedance mismatch' ! - (Ashton)
         You didn't specify stateful or stateless system - (drewk) - (2)
             Stateful. - (admin) - (1)
                 Then the issue is multi-column constraints - (drewk)
         Neat idea, but marginal in practice - (JayMehaffey)

s/\$lrpd_saying/This space intentionally left blank./g
90 ms