From: Romano <me+unobe@fallglow.com>
To: 9front@9front.org
Subject: Re: [9front] ndb doc patch
Date: Wed, 19 Jun 2024 22:00:17 -0700 [thread overview]
Message-ID: <1DD347016319C412B78377B0244084CF@smtp.pobox.com> (raw)
In-Reply-To: <8124838e-a6a3-41ea-9169-5a5fe42347fc@posixcafe.org>
On Wed Jun 19 14:30:21 -0700 2024, moody@posixcafe.org wrote:
> On 6/18/24 12:35, Romano wrote:
> > Hello list,
> >
> > At the end of last year I had a small patch
> > for ndb's man page. There was a bit of
> > discussion re: it in January ( https://inbox.vuxu.org/9front/39A39E500516DB6E2B4CE0BC27677DEF@eigenstate.org/ )
> > and I have tried to address Ori's suggestion
> > here: http://okturing.com/src/20100/body
>
> I would probably much prefer to fix this than to document a bug.
> If anything should change regarding this, it should be picking a
> sensible maximum and then documenting it in ndb(6) as part of the
> file specification. Not in ndb(8) as a bug of the implementation.
Yeah, I that would be preferable but I thought at least documenting
the known behavior that could trip someone else would would be okay.
Instead of documenting tho', the attribute name should not be limited
to 32 bytes (and not silently truncated) but I'm not sure what a
sensible maximum is. The attribute values as far as I can tell will
happily consume as much memory as possible, and Ndbvlen (as Ori
pointed out) is just a starting default.
For the line parsing limitation of 8K, do you think that is
also something that should be fixed or something that is OK to
document as a limitation?
prev parent reply other threads:[~2024-06-20 5:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 17:35 Romano
2024-06-19 21:28 ` Jacob Moody
2024-06-20 5:00 ` Romano [this message]
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 \
--in-reply-to=1DD347016319C412B78377B0244084CF@smtp.pobox.com \
--to=me+unobe@fallglow.com \
--cc=9front@9front.org \
/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;
as well as URLs for NNTP newsgroup(s).