On Sun, Apr 14, 2019 at 3:56 PM Chary Chary <[email protected]> wrote:
> Martin, > > great that you share your future plan. > > >> (I think of the next version as essentially a rewrite in 3 parts: (1) >> rewrite just the core in C++ keeping the very same schema and same Python >> API but with protobufs instead of namedtuples as storage (cross language), >> > > Will it still be possible to write plugins? > Yes, same API, but potentially also C++ support. > > >> (2) fork the SQL query tool to its own project, adding missing features >> and making it able to work on any data, not just Beancount, >> > > what kind other "any data" do you have in mind? I understood, that bean > query was made specific to double entry accounting-like data. > Any other data. At the very least, anything that can be converted a flat list of rows and columns of basic types. The only thing specific to double-entry accounting-like data in bean-query is the aggregation functions for Position and Inventory types, and their associated rendering routines. The vision I have for this is to generalize it to any data (e.g. csv files, any protocol buffer type, other sources of data, e.g., metadata on images, html tables from web pages) and to allow the addition of custom types to this tool, which is what Beancount would use, + the addition of convenient features for reporting (built-in pivot clause, and aggregation of columns as a special "bottom" line). This scope would be that of a data science tool, beyond the scope of Beancount. As long as it's customizable enough that wouldn't be a problem. One of the central aspects of this tool which has been underserved by other data science frameworks is the automatic inference of schemas; this should, ideally, just work. Ideally you should be able to run joins and filters on a good old CSV file. -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/CAK21%2BhM62vomPcBDRxuxSFDai2sYz9BxA%2BHK-6%2BDKMFFTfxyTw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
