Rounding in the price db.

[David Carlson]

 I have been watching this thread and am glad that this discussion is
happening.

The price db  is also used in the reconciliation dialog when reconciling an
account with subaccounts. The reconciliation dialog appears to use the most
recent value, where I would expect it to use nearest in time to the
reconciliation date.

Would there any value to keeping one price from each source as opposed to
only one value?  Also, is it possible to have securities valued in more
than one currency?

On Mon, Aug 17, 2015 at 5:06 PM, John Ralls <jralls at ceridwen.us> wrote:

>
> > On Aug 17, 2015, at 8:07 PM, Mike Alexander <mta at umich.edu> wrote:
> >
> >> On Aug 17, 2015, at 5:36 AM, John Ralls <jralls at ceridwen.us> wrote:
> >>
> >>
> >>> On Aug 12, 2015, at 2:13 PM, John Ralls <jralls at ceridwen.us> wrote:
> >>> It might help to consider what the price db is used for: Aside from
> providing a default rate in the transfer dialog, it’s used for pricing
> assets in the Accounts page and the summary bar — only the latest entry is
> used there. It’s used for calculating values in reports, where the reports
> can use a weighted average, nearest in time, most recent, or average cost.
> I need to look to see if the average cost actually looks at the buy
> transactions or if it does something similar to nearest in time and at
> weighted average to see what it’s averaging and how it’s weighting the
> averaged values. Depending on what those two are doing might drive whether
> multiple F::Q entries per day make sense, assuming that the algorithms make
> sense.
> >>
> >> OK, I’ve looked. They don’t use the price db, which is what one would
> expect. Weighted-average is weighted by the transaction size, which will be
> distorted by stock splits but is otherwise OK.
> >
> > The Advanced Portfolio report uses the Price DB to get the current value
> of a holding.  There is an option to use a transaction price instead, but
> the default is to use the Price DB.  The only Price DB options it supports
> are "latest" and "nearest in time".  If you ask it to use a transaction
> price (or if it can't find a price in the Price DB) it uses the most recent
> transaction which defines a price that can be converted to the report's
> currency.
> >
> > I can't speak for other reports.  I'm out of town and don't have easy
> access to the source code.
>
> I was referring only to the “average” and “weighted average” options
> provided by price-quotes.scm and really only concerned about whether or not
> they would affect or be affected by mods to what we store in the price db.
> I don’t think they will, so I’ll proceed with what we’ve discussed already.
>
> Regards,
> John Ralls
>
>
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>