3 ms·
Currently yes. hledger has rudimentary SQL export (https://hledger.org/hledger.html#output-format https://hledger.org/hledger.html#output-format).
by smichael 5y ago
Currently yes. hledger has rudimentary SQL export (https://hledger.org/hledger.html#output-format https://hledger.org/hledger.html#output-format).
- jolmg 5y agoIt'd be cooler if the quantities didn't come formatted with thousands seperator commas and currency symbols. Then, the numbers could more easily be treated as numbers in SQL.
- smichael 5y agoI have not used the SQL output, but I hope it's like all other hledger output: the number formatting is configurable (following your data format by default, but overrideable).
- jolmg 5y agoYeah, but IMHO, while it makes sense to have configurable formatting for terminal output, it doesn't make sense to apply that formatting to output meant for SQL.
- smichael 5y agoTrue! I will look into it, thanks for the report.
- jolmg 5y agoOh, Simon Michael! I hadn't noticed your username until now. > I have not used the SQL output. I've used it to process the register output in a pipeline. Sometimes, my `hledger reg` queries result in multiple quantities on some transactions. The terminal output leaves the columns of the date, transaction description and account blank, for pretty-printing purposes, I suppose. Those blanks complicate adding up the quantities per transaction using a tool like awk. There's also the JSON output format, but the depth of the objects around quantities makes the CSV still simpler to process, even though I need to process the quantities' text in SQL so they can behave like quantities. Just sharing how one user uses hledger.
- smichael 5y agohttps://github.com/simonmichael/hledger/issues/1684 https://github.com/simonmichael/hledger/issues/1684