> Don't be sorry or discouraged! Sometimes things like this force us to remind > ourselves why things are designed the way they are. I've been tempted to make > this > very change more than a few times recently... > > I have to admit i'm not happy with the current behaviour, however i understand your reasoning, and you've obviously given this a lot of thougth, so until someone comes up with a better solution, it's probably for the best to keep it this way.
It's the most annoying problem in dabo...semi-filled forms, of course they are mostly fixable, but this default behaviour of raising an exception is just not enough in my opinion, the end user has no clue something bad has happened, and end up messing up the data, this is quite notorious in one of my apps where the dbadmin has the BAD habbit of changing, and deleting info directly on the DB...as my app is..as he says... too restrictive, leaving me with a bunch of incoherent data. This is obviously a worst case scenario situation, but that CAN happen, and when it does... i think the current dabo behaviour is dangerous... I'll give it some extra tought and ask you opinion prior to commit Regards, Pedro _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
