ajit_cus wrote: > > Hi, > I found a description of my problem in the archives: > > http://listserv.sap.com/pipermail/sapdb.general/2002-August/01 3003.html > ...... > >>Grrmmph, you are right. It is a bug with those values > having 12 as hour-value. > >>for 1..11 it is ok, no matter if AM or PM. But those > special 12-behaviour > >>was not done correctly. Sorry, will be corrected with the > next version. > > >>For those who do not know the US-like date-format (used with SAP DB > >>datetimeformat USA or if specifying PM/AM in TO_DATE in > sqlmode Oracle) > >>by heart: > > >>Remembering that AM is between midnight and noon and PM is > between noon and midnight > >>is correct, but confusing combined with hour 12: > > >>12:01 AM .. 12:59 AM --> 00.01 .. 00.59 the first hour of the day > >>01:00 AM .. 11:59 AM --> 01.00 .. 11.59 the next minute > after 12:59 AM is 01:00 AM ! > >>12:00 PM .. 11:59 PM --> 12.00 .. 23.59 afternoon and > evening, but again starting with 12, 1, 2, >>..., 11 > > >>And this special 12 causes/caused the problem in our code. > > >>Elke > >>SAP Labs Berlin > > Has the bug been fixed and which version contains the fix? I > am using 7.3.0.25. Due to the bug a table of mine is no > longer accessible.Please reply ASAP. > regards and thanks,
fixed with 7.3.0.29 which is available Elke SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
