Yes.
The terminology you use is a bit different than the one I usually refer to, but I think we're saying the same thing.
Transaction
Posting1 Amount1
Posting2 Amount2
Posting3 Amount3
where "Transaction" stands for some fields of the transaction selected and "Posting" some fields for the posting, would result in
Transaction Posting1 Amount1
Transaction Posting2 Amount2
Transaction Posting3 Amount3
The problem I was alluding to is that if you render repeated values, such as links or balance (a balance is of type "Inventory", which is a list of positions), the default table rendering would do this:
Transaction Posting1 Amount1 BalancePosition1
Transaction Posting2 Amount1 BalancePosition1
...
I changed the default to render inventories like this:
Transaction Posting1 Amount1 BalancePosition1.BalancePosition2
Transaction Posting2 Amount1 BalancePosition1,BalancePosition2
It just makes a large balance cell, but it's more rational and it's what I always thought it should be.
Besides, if you have only a single currency, or if you convert to one (or market value), the inventory in the balance would have a single position and it wouldn't matter.
The shell now has an "expand" shell variable to control this and keep the old behavior. (Eventually I'll probably fold this into the SQL syntax itself, I think that's where it deserves to be.)
So, it turns out I recently was on vacation with my girlfriend and she was complaining tonight that my export of our expenses were difficult to review in text format, so after doing this I had a quick go at implementing CSV rendering for bean-query and so I did it... it works. bean-query now takes a -f/--format=csv option and you should be able to import that into a spreadsheet.
Note the existence of the upload-csv-google-sheet in Beancount, which allows me to provide an existing Sheets doc id and a list of filenames, and the script creates sheets automatically, uploading all the data. This is convenient. I just used it to share our vacation expenses. (It can be a little flaky but it works; I need to convert it to the recently released new Google Sheets API, at the moment it's using gdata, which is ancient, but still sort of works).
There's a final twist: Not expanding rows by default is probably not enough in some cases. If you select a column of type Amount (like "units", or "cost"), the value rendered will be the number and its currency in a single cell, like this: "324.34 USD". Importing this in a column won't make it possible to do calculations on it. What you could do is just select the number. Anyhow, I think I'll implement that behavior (rendering Amount's number and currencies as two columns) and add another option for this soon.
I hope this helps,