181 question

Actually Andy, it seems you have hit a slight bug here. Without
testing I am saying that it is not the notify attribute that could
have caused the mail to be sent (it comes after the date checking) but
the maintainer notification. I'll run some tests either later this
weekend or coming week and perhaps change the order of the tests
around to make it do the right thing.

-Marten

Andrew Adams <ala at merit.edu> writes
 * 
 * Hi.  Lately I've been playing quite a bit with the new 181 software
 * to see more how things work, etc.  (Things look really cool by the way!)
 * I noticed the following behavior and wondered if it was by design. 
 * 
 * I tried to change an object with an older 'changed' date that the one 
 * currently in the db.  The message that was mailed out to the people
 * specified in that object's 'notify' attribute said that the
 * object had been _replaced_.  However, the object wasn't really replaced.
 * That is to say, the software realized that I was submitting an object
 * with an older 'chagned' date and prevented me from making the update.
 * 
 * So it seems to me that the message sent to the people specified in the 
 * 'notify' should read 'a change was _attempted_', yes?
 * 
 * 
 * Thanks,
 * 
 * Andy
 * 



-------- Logged at  Mon Jan 16 13:50:57 MET 1995  ---------