Hi List,

I've got a weird problem using SapDB 7.4 and PHP.

We're saving bookings in our Database. Besides the booking data we also save
a timestamp so we always know the exact time a booking was initiated.

Our booking department, which reads and completes the bookings, has a
refreshing window, which alerts via JavaScript, when a new booking was
inserted in the database.
Herefore we have a table saving the last timestamp when the refresher was
loaded. This means: I compare the booking time and the time the refresher
last loaded. Thereofore I use the condition WHERE
TIMESTAMP(BOOKING.BOOOKINGTIME) > TIMESTAMP(CHECK_NEW_BOOKINGS.LASTREFRESH)

And here I noticed the problem:

We insert the booking Like INSERT INTO BOOKING VALUES (...,NOW(),...)
We also make an INSERT INTO CHECK_NEW_BOOKINGS VALUES (EVENTID,NOW())

The mysteroius thing is: the NOW() parameter inserts two different
timestamps into these two tables.

For instance, if we load the refresher first, it inserts as timestamp
"2005-09-01 10:22:22.7591558".
Now, directly after the refresher loaded, we insert a booking but the
timestamp is about 17 seconds earlier than the timestamp inserted by the
fresher. ("2005-09-01 10:22:05.137049").

I also noticed, that the database timestamp is about 2 seconds earlier than
the current system/hardware time.

I hope you can help me, I really don't have a clue what this could be.

Thanks alot!

Jan Lendholt



--
Softwaredevelopment
SKYBOX Management GmbH
Barmbeker Straße 2
D-22303 Hamburg
 
+49 40 27 07 51-25 Tel
+49 40 27 07 51-14 Fax
 
[EMAIL PROTECTED]
 
www.rentaskybox.de
www.skyboxmanagement.de
 
The information contained in this communication is confidential and is
intended only for the use of the recipient named above, and may be legally
privileged and exempt from disclosure under applicable law. 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 resend
it to the sender and delete the original message and any copy of it from
your computer system. Opinions, conclusions and other information in this
message that do not relate to our official business should be understood as
neither given nor endorsed by this company.


--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to