https://bugs.freedesktop.org/show_bug.cgi?id=50575
--- Comment #2 from Lionel Elie Mamane <lio...@mamane.lu> 2012-06-07 06:57:47 PDT --- (In reply to comment #1) > The wrapper between Base and ODBC has to: > - multiply hundredths of a second with 10^7 to be stored in struct > tagTIMESTAMP_STRUCT.fraction > - divide by 10^7 when reading tagTIMESTAMP_STRUCT.fraction to receive > hundredths of seconds. This way all values written by Base can be read and > used > without issue. AFAIK, it does that. > Problems arise only with third party data that are more precise than Base's > internal data type. This can happen with any database driver, not just ODBC. > When those data are used as primary key, Base has no way to address one > specific row because its internal representation lacks essential data. This > cannot be solved. Well, going to nanosecond precision in Base should cover nearly all cases. I think most databases don't have timestamp resolution finer than nanoseconds :) > In this bug the situation is much simpler. The timestamps in my tables are > have > no fractions of seconds, so the fraction structure element is always 0. My > guess is, that Base is failing in translating ODBC timestamps to Base > timestamps and/or vice versa. Oh, your timestamps have no fractional part? Then indeed, there is another bug somewhere. I'll try to take a look. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
