Ed Leafe wrote: > The bizobj will only usually have a small subset of all the records in > the table, so it's going to end up having to make a database call anyway. > > Unless there was a good reason to do otherwise, I'd catch the > DBQueryException and handle that. In a multi-user scenario, you'd end up > having to do that anyway. > Ed,
You think that's better than writing a select statement query with a where clause that filters on the column value? I want to try to incorporate the uniqueness validation inside the validateRecord because I do all the validation there and display all the errors to the user at once on the dialog. I would still handle the DBQueryException, I would just want a way of bundling the uniqueness check in with the other business rules. Regards, Nate _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
