Re: Importing transactions from bank.

[mployby]

I've started playing with import scripts,the sample files provided in repo 
are very useful, just have couple of additional questions i was not able to 
figure out/not 100% sure about:

1 bean-extract does not write transactions in main beancount file 
(personal.beancount), it generates output into command line or 
tmp.beancount and we enter them manually, right?

2 when running  "bean-extract -e BEANCOUNT_FILE" what is the algorithm used 
to check duplication? Does it check only for same amounts? Or also takes 
into consideration additional clues (payee, date range, etc)?

3 When filing files bean-file example.import ../Downloads/ -o documents/ 
how are name and date generated?
Seems it is picks up date from original file name (example 
UTrade20160215.csv), but when it's not in file name how ofxdownload.ofx 
turns to 2013-12-18.bofa.ofx

4 Main value of regression testing is to insure that new changes/additions 
to importers still work with old input files,
It's not so useful to help importers work with new formats if format was 
changed by bank, right?

On Monday, April 9, 2018 at 4:28:30 PM UTC-4, Michael Droogleever wrote:
>
> You'll need to use something like this, 
> https://gist.github.com/mterwill/7fdcc573dc1aa158648aacd4e33786e8#file-importers-chase-py,
>  
> or make your own: 
> https://docs.google.com/document/d/11EwQdujzEo2cxqaF5PgxCEZXWfKKQCYSMfdJowp_1S8/edit
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To post to this group, send email to beancount@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/57580546-5574-4004-9794-4c3dd6f99812%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Issue #281: Query "id" column does not identify transactions uniquely (blais/beancount)

[Vincent Vu]

New issue 281: Query "id" column does not identify transactions uniquely
https://bitbucket.org/blais/beancount/issues/281/query-id-column-does-not-identify

Vincent Vu:

I'm trying to use BQL to get transactions from my journal into R for analysis, 
and have run into a problem with identifying transactions.  According to the 
BQL documentation the "id" column should identify transactions uniquely.  
However, this fails if two distinct transactions have exactly the same content.

As an example of when this (reasonably?) occurs, my wife and I belonged to the 
same gym for a few years, and that gym charged our credit card twice on a 
monthly basis for the exact same amounts.  The content of the imported 
transactions are identical, but they are actually distinct.


-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To post to this group, send email to beancount@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/20180415192322.7199.28845%40celery-worker-110.ash1.bb-inf.net.
For more options, visit https://groups.google.com/d/optout.

Re: Timezones and price fetcher

[Martin Blais]

On Sun, Apr 15, 2018 at 12:51 PM, Martin Michlmayr  wrote:

> * Martin Blais  [2018-04-11 16:29]:
> > You ask at 14:00 in which timezone? US 14:00 or Europe 14:00?
> > If you don't know the instrument trades in the US, you ask at 14:00 in
> > Europe timezone?
>
> Sorry, I thought you told the API "I want the exchange rate at 14:00
> time".  If so, we'd all get the same answer regardless of our local
> timezone.  It would be nice to know what the APIs timezone is so we
> know what "14:00" really means but that doesn't matter for beancount.


> If you only tell the API "I want the exchange rate now", then I think
> beancount should store the time in UTC.
>

If you store the timezone, there's no ambiguity.

I made a couple decisions staring at this long enough:

- The API will accept a time, not a date. bean-price will be in charge of
deciding how to convert that (and for now, using the local time, because
problems highlighted in prior discussion).

- All the datetime instances have to be aware. No more usage of naive
datetime instances anywhere. (I'm coming around to think that support naive
datetimes in the Python datetime module API is a design flaw.)




>
> > Our current API doesn't support you providing a time, just a date.
> > You request for a price at a particular date.
>
> Ok, (I think) I see the problem.
>
> If the API queried by beancount only provides 1 rate per day, we could
> easily find out what a "day" is according to them by doing a query
> every hour for 24 hours.
>
> Or just pick mid-day UTC.
>
> --
> Martin Michlmayr
> http://www.cyrius.com/
>
> --
> You received this message because you are subscribed to the Google Groups
> "Beancount" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beancount+unsubscr...@googlegroups.com.
> To post to this group, send email to beancount@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/beancount/20180415165103.zaixqwtthtn35fuu%40jirafa.cyrius.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To post to this group, send email to beancount@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/CAK21%2BhN6F7atoQ1ie7Mo_8FuUhw9hhogexL1a%2BpfcMpnOwOQ8w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Timezones and price fetcher

[Martin Michlmayr]

* Martin Blais  [2018-04-11 16:29]:
> You ask at 14:00 in which timezone? US 14:00 or Europe 14:00?
> If you don't know the instrument trades in the US, you ask at 14:00 in
> Europe timezone?

Sorry, I thought you told the API "I want the exchange rate at 14:00
time".  If so, we'd all get the same answer regardless of our local
timezone.  It would be nice to know what the APIs timezone is so we
know what "14:00" really means but that doesn't matter for beancount.

If you only tell the API "I want the exchange rate now", then I think
beancount should store the time in UTC.

> Our current API doesn't support you providing a time, just a date.
> You request for a price at a particular date.

Ok, (I think) I see the problem.

If the API queried by beancount only provides 1 rate per day, we could
easily find out what a "day" is according to them by doing a query
every hour for 24 hours.

Or just pick mid-day UTC.

-- 
Martin Michlmayr
http://www.cyrius.com/

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To post to this group, send email to beancount@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/20180415165103.zaixqwtthtn35fuu%40jirafa.cyrius.com.
For more options, visit https://groups.google.com/d/optout.

Re: Timezones and price fetcher

[Martin Blais]

On Thu, Apr 12, 2018 at 2:15 AM, Justus Pendleton 
wrote:

> I don't see "lining up with markets" as a necessary condition since that's
> poorly defined for dealing with other timezones anyway.
>
> If I run bean-price when the market is open I'm going to get a quasi-real
> time quote that is delayed an arbitrary and possibly unknown amount of time
> anyway. It won't **really** be the price at 12:07pm. (This will vary
> depending on the source and the price fetcher, of course.)
>
> Just using the user's timezone seems to make the most since to me. But
> what happens with downloaded prices when the user moves to a different
> timezone?


Nothing changes.



> Or is the timezone going to be stored with the fetched price?
>

No, unless there's a good reason to.
That would break things (dates changing unexpectedly).
Want to keep it simple.




--
> You received this message because you are subscribed to the Google Groups
> "Beancount" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beancount+unsubscr...@googlegroups.com.
> To post to this group, send email to beancount@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/beancount/c6450704-b02f-4698-9b5f-b0dc8d699f75%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To post to this group, send email to beancount@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/CAK21%2BhPRqX4YkgkW3nAxGFR2ekffv1oDvpdXSzQHtBvRiCUD6A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.