Re: auto update dates
От | Joel Burton |
---|---|
Тема | Re: auto update dates |
Дата | |
Msg-id | JGEPJNMCKODMDHGOBKDNMEFICPAA.joel@joelburton.com обсуждение исходный текст |
Ответ на | auto update dates (Rory Campbell-Lange <rory@campbell-lange.net>) |
Ответы |
Re: auto update dates
|
Список | pgsql-novice |
> Hi Joel. > > [For other readers: I'm trying to learn how to update the modified date, > time and timestamp fields in my database - I've deleted the old parts of > the mail as it was getting too long.] > > Thanks a stack for your mail. I've just about got it working! I have a > problem with time typing - if I make this function to just update the > date it does not work. > > create function update_date_time() returns opaque as > 'begin > new.d_modified = current_date; > new.t_modified = current_time; > new.ts_modified = current_timestamp; > return new; > end' language plpgsql; > > create trigger ideas_update_date_time > before update > on ideas > for each row execute procedure update_date_time(); > > brandf=> update ideas set title = 'three' where title ~ 'one'; > NOTICE: Error occurred while executing PL/pgSQL function > update_date_time > NOTICE: line 3 at assignment > ERROR: Bad time external representation '16:11:45.820720+01' current_time returns timezone information, but you're trying to store this in a field that is time w/o timezone information. either coerce this data yourself, or make the field hold timezone info. Better question, though: why are you storing the date, the time, and the timestamp? Much easier to simply store the timestamp. You can always get the date & time from that. This will save you space _and_ time. (Plus, your current problem would become irrelevant). - J. Joel BURTON | joel@joelburton.com | joelburton.com | aim: wjoelburton Knowledge Management & Technology Consultant
В списке pgsql-novice по дате отправления: