Another small question:
On Thursday, September 5, 2024 at 6:19:37 PM UTC+2 [email protected] wrote: > So, > > select date, account, narration > > Gives the same result as > > select entry.date, account, entry.narration > > Question: why is it done like this? What is the reason to have > transaction information (e.g. date ) both in posting as well as in > posting.entry? Just backward compatibility. The old way of doing things will be deprecate and eventually removed to make the data model more consistent and "orthogonal". However, the capability of accessing fields of structured types in beanquery has only beed recently (compared to how much time I can dedicate to the project) introduced, and before starting to emit deprecation warnings I want to have some documentation in place, and I haven't had time to work on the documentation. Thus for now we live with the duplication. So, the long term plan is to support only this notation: select entry.date, account, entry.narration and drop down support for this notation: select date, account, narration Is this correct? -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/beancount/a404acec-fa69-4f18-b922-413974aef41dn%40googlegroups.com.
