Query structure #4

New Issue

2016-04-14T15:25:42-05:00

mattbk commented

2016-04-14 15:25:42 -05:00

(Migrated from github.com)

Using aggregate() makes things a lot simpler, but still need some functions to turn bookkeeping questions into aggregate() queries. What are the things we need to group or query by?

class (in the Quickbooks sense; also could be called tag or category)
account (in the QB/ledger sense; where the double-entry-ish part comes in)
dates range
Bank (maybe nonstandard; not sure how double-entry would do this; for now have one sheet for each bank)
Type (from QB; not sure if this is necessary or not)
Reconciliation.Status
whether or not we want to include a total line item (function output, not aggregate() input)

Anything else?

Comparative queries on

Debit
Credit

Text search queries on

Ref.No.
Payee

- Memo

It's also possible that table filters could be used for some of these, but those probably aren't as easy to save/export.

Using `aggregate()` makes things a lot simpler, but still need some functions to turn bookkeeping questions into `aggregate()` queries. What are the things we need to group or query by? - `class` (in the Quickbooks sense; also could be called `tag` or `category`) - `account` (in the QB/ledger sense; where the double-entry-ish part comes in) - `dates` range - Bank (maybe nonstandard; not sure how double-entry would do this; for now have one sheet for each bank) - Type (from QB; not sure if this is necessary or not) - Reconciliation.Status - whether or not we want to include a `total` line item (function output, not `aggregate()` input) Anything else? Comparative queries on - Debit - Credit Text search queries on - Ref.No. - Payee ## \- Memo It's also possible that table filters could be used for some of these, but those probably aren't as easy to save/export.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: matt/ledgerr#4