How about... items.replacementpricedate and items.datelastseen defaulting to now() as well? These changes will allow me to clean up SQL in Biblio.pm which sets these fields to now(). And as far as I can see will not cause problems with regular data entry of new records. On 11/15/07, Paul POULAIN <paul.poulain@free.fr> wrote:

Chris Nighswonger a écrit :

...

Hi all, Does anyone see any reason not to default biblio.datecreated to now()?

Not me (I don't see any reason not to do thas => I agree to do it ;-) )

-- Paul POULAIN, consultant senior BibLibre SARL Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19

-- Chris Nighswonger Faculty Member Network & Systems Director Foundations Bible College & Seminary www.foundations.edu www.fbcradio.org ------------- NOTICE: The information contained in this electronic mail message is intended only for the use of the intended recipient, and may also be protected by the Electronic Communications Privacy Act, 18 USC Sections 2510-2521. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please reply to the sender, and delete the original message. Thank you.