Introducing several updates a day when the 'changed' attribute has a granularity of 1 day can result in inconsistancies in the database when you use email for the update. More than 1 update a day should be avoided in your current implementation. Laurent PS: Yes Tony "The software allows more than one update a day": - i send a update at 15:00, but i have email problems and the mail is delayed 1h (common value with sendmail). - i send a update at 15:20 because i realized i did a typo. The email problem is gone and the mail is not delayed. - The result is left as an exercise for the reader :-) Actually i am wondering if 'dbupdate' check the date in the email header?
This is not for us to decide. The database working group should decide on this. However, your statement that the document only allows one update per day is wrong. The current database can take as many updates per day for one object as you like. Implementation matter.
-Marten
-- Laurent Joncheray, E-Mail: lpj@merit.edu Merit Network Inc, 1071 Beal Avenue, Phone: +1 (313) 936 2065 Ann Arbor, MI 48109, USA Fax: +1 (313) 747 3745 "This is the end, Beautiful friend. This is the end, My only friend, the end" JM