Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #100321 > unrolled thread

Re: Problem with sqlite3 and Decimal

Started by"Frank Millman" <frank@chagford.com>
First post2015-12-12 08:22 +0200
Last post2015-12-12 08:22 +0200
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Problem with sqlite3 and Decimal "Frank Millman" <frank@chagford.com> - 2015-12-12 08:22 +0200

#100321 — Re: Problem with sqlite3 and Decimal

From"Frank Millman" <frank@chagford.com>
Date2015-12-12 08:22 +0200
SubjectRe: Problem with sqlite3 and Decimal
Message-ID<mailman.172.1449901375.12405.python-list@python.org>
"Chris Angelico"  wrote in message 
news:CAPTjJmoPXFSnXe1QA8MjjncBZBpqNkztha8YHJv=MBm--ZE8jg@mail.gmail.com...

> On Sat, Dec 12, 2015 at 4:10 PM, Frank Millman <frank@chagford.com> wrote:
> > I can reproduce your example above. However, if I set the initial value 
> > to
> > 5678.7, then the sequence goes
> >
> > 5678.7
> > 5802.15
> > 5925.6
> > 6049.05
> > 6172.5
> >
> > I would have thought that adding 123.45 to 5802.15 would always produce 
> > the
> > same result, but here it seems to depend on prior events.
> >
> > Any idea why? Academic interest only, but I am curious.
>
> You weren't adding 123.45 to 5802.15. Here's why.

[snip really interesting explanation]

Wow, thanks for that, Chris. Consider my academic curiosity well and truly 
satisfied :-)

I have found a workaround for my problem, but I will post that in a separate 
message - still testing to make sure it is 100%.

Frank

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web