From: Ammar Faizi <[email protected]>
To: Alviro Iskandar Setiawan <[email protected]>
Cc: GNU/Weeb Mailing List <[email protected]>
Subject: Re: [RFC] GNU/Weeb Financial Transaction Record Design
Date: Wed, 15 Jun 2022 17:03:35 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAOG64qP9T2aCBPEgE7L-00S1ogh+mBkhU3-nej-4rxvdXQRQaQ@mail.gmail.com>
On 6/15/22 5:00 PM, Alviro Iskandar Setiawan wrote:
>> 2) How do we maintain a new field in the future if we ever add more?
>
> Maybe just make them be an empty string. Appending an empty string
> won't change the hash because it doesn't change anything. For example,
> we create a new field x, make it nullable, if it's NULL then when
> we're validating the old records that don't have this field just treat
> it as an empty string, it won't change the hash, so it's backward
> compatible.
Not sure how will it look like. I am looking forward to the patchset then.
--
Ammar Faizi
next prev parent reply other threads:[~2022-06-15 10:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 9:21 [RFC] GNU/Weeb Financial Transaction Record Design Alviro Iskandar Setiawan
2022-06-15 9:23 ` Alviro Iskandar Setiawan
2022-06-15 9:42 ` Ammar Faizi
2022-06-15 10:00 ` Alviro Iskandar Setiawan
2022-06-15 10:03 ` Ammar Faizi [this message]
2022-06-15 10:06 ` Alviro Iskandar Setiawan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox