If you wanted to get really radical each transaction could be a separate
timestamped-to-the-second file and then have them all included with a glob.
That would ensure that git (or whatever other VCS you use) would do the
right thing.

On Sun, Apr 16, 2017 at 3:12 PM, Simon Michael <[email protected]> wrote:

> On 4/16/17 11:28 AM, Taylor R Campbell wrote:
>
>> Date: Sun, 16 Apr 2017 11:05:16 -0700
>>> From: Simon Michael <[email protected]>
>>>
>>> On 4/13/17 6:39 AM, Antoine Beaupre wrote:
>>>
>>>> But I can't imagine running 100 transactions per day in ledger-cli. I
>>>> can't think of how I would allow for multiple to add transactions
>>>> simultaneously. Git? I already have merge conflicts with myself, and
>>>> they are not fun...
>>>>
>>> Interesting discussion. On the above point, purely from a technical
>>> perspective, aren't transactions just a file append ? We have a number
>>> of curses and web UIs which can add transactions, 10000 a day shouldn't
>>> be a problem and no Git required.
>>>
>> If you're considering multiple Unix processes trying to append to a
>> file simultaneously, that doesn't work very well unless they
>> voluntarily cooperate with a file lock.
>>
>> If you have multiple users appending to their local copies and
>> committing to Git, so that there is an audit trail for every change to
>> the ledger, then they will get conflicts when they try to merge into a
>> central repository.
>>
>> In both cases, you can work around this by having each process/user
>> edit their own private files, and then `merge' them by including them
>> in a common ledger file.
>>
>> Might be nice if ledger could also do `include *.ledger' or something;
>> then you could use a separate file per transaction or group of
>> transactions without having to specify it up front.  But there's no
>> globbing in `include'.
>>
>>
> For a concrete example, I was imagining multiple users adding transactions
> via hledger-web (http://demo.hledger.org/journal?add=1). Simultaneous
> adds will probably "never" happen in practice, and if they did, I expect
> going through a web app sequentialises them nicely.
>
>
>
> --
>
> --- You received this message because you are subscribed to the Google
> Groups "Ledger" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to