> Is this a bug in MySQL 3.23.37? Could it have something to do with my OS
> (OpenBSD 2.9)? Or am I doing something wrong with the statement "update
> time_worked set total = start - finish;"?
Umm. Don't you mean 'finish-start'?
--
Amer Neely [EMAIL PROTECTED]
Softouch Information Services: w
You must make sure you don't perform arithmetic differences between integer
values such as "2000" representing 8:00 pm and "1945" representing 7:45 pm
because that obviously would result in wrong values. For example 2000-1945=55,
which is arithmetically correct but not the desired result if you wa
I was using float...but even when I changed it to time, MySQL still gave me
odd values on those rows. What type should I use?
Alex Kirk
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http
Depends on the column type -- what column type do you use for storing
the time values?
Bogdan
Alex Kirk wrote:
> Is this a bug in MySQL 3.23.37? Could it have something to do with my OS
> (OpenBSD 2.9)? Or am I doing something wrong with the statement "update
> time_worked set total = start - f
I've got a table that's acting as a timesheet, with time began and finished
in each record. In order to do up an invoice based on that, I was making a
total time field, which was just finish - start. It worked great for all of
the records but two, where I had this result:
1 -- Start: 19:45:00
