Użytkownik Ed Leafe napisał: > So am I correct that you want to have default values set in both the > bizobj *and* in the database? If so, am I the only one who thinks that this > is a very brittle design? > > The reason the check is there is to avoid unnecessary traffic to the > database. IOW, if your bizobj has already handled the default values, there > is no need to call the database for each new record a second time. But it > sounds to me like you want the bizobj to only handle some of the logic, and > let the database handle the rest? >
Almost all fields are set to default in framework: dates, amounts, etc. But there are (usually no more than one per table) fields that are very important. They are document reference symbols, which are very specific fields. Since documents are restricted, these fields: - must be unique - numeration must be continuous without missing values - can't be changed or removed. Now it's done in single stage operation/transaction on backend. I can split this process and save record and then get reference from backend as stored procedure and update table but risk of failure increases. And there must be nested transaction involved. Now I'm still researching how to resolve this safely. -- Regards Jacek Kałucki _______________________________________________ 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]
