On 5/30/12 12:28 PM, Simon Michael wrote:
Not in any way, please keep going. :) Yes to what you said. I think free editing of the journal content (as opposed to structured editing through an API) is incompatible with long-lived ids. Perhaps the best one could do is have it attach ids to each txn (& posting ? :/ ) as metadata tags when you first upload the journal content. Thereafter editing is done using the API, or when free editing is allowed you trust the user to preserve the id tags as they edit.
PS or you just forget about the editable text format for this application and store things in a db, by selecting a different backend storage option or doing a one-time conversion. Supporting different storage back ends is quite a jump from *ledger's original essence, but it would be nice to have at some point.
