Re: Problem with sqlite3 and Decimal

From	"Frank Millman" <frank@chagford.com>
Newsgroups	comp.lang.python
Subject	Re: Problem with sqlite3 and Decimal
Date	2015-12-12 08:22 +0200
Message-ID	<mailman.172.1449901375.12405.python-list@python.org> (permalink)
References	<n4ei3l$b98$1@ger.gmane.org> <CAPTjJmor6NewucCo7XTSSwyyfbgwCWZ8Jt-MjjkYSjOCFu78_A@mail.gmail.com> <n4ga7r$gil$1@ger.gmane.org> <CAPTjJmoPXFSnXe1QA8MjjncBZBpqNkztha8YHJv=MBm--ZE8jg@mail.gmail.com>

Show all headers | View raw

"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

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

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

csiph-web