Mailing-List: contact user-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Users List" <user@commons.apache.org>
MIME-Version: 1.0
In-Reply-To: <C7CFFB1B-DC56-418C-991E-08D7C0D6C052@apache.org>
References: <CAKQZcJofDF9ekQtL2R77ZdSmgPcUBX4pAaZXw4HqAd7nf7aocA@mail.gmail.com>
 <CACZkXPycicBfOOqkPSo6jqfm=o+X89c+UKy_XzcvEWiMcY9ivg@mail.gmail.com>
 <CAKQZcJqjdgiCgBqyLsL=jzDi9k4PqOmt7nZ6eataKJe1ZQUSdA@mail.gmail.com>
 <CACZkXPx+gD=5_mNtA04csP9RD6PzHv7Y1R9T3GwekmjMaDxfCw@mail.gmail.com>
 <CACZkXPxOpkb1Wzyooi4dRZEQJbY+hJf=W8YETFva8C7CJJ=3aw@mail.gmail.com> <C7CFFB1B-DC56-418C-991E-08D7C0D6C052@apache.org>
From: Gary Gregory <garydgregory@gmail.com>
Date: Tue, 15 Aug 2017 08:01:53 -0600
Message-ID: <CACZkXPwDfj-Kaimtu9Pqd1_cFsVs57+GyCneSfDR-SBtnuTNXw@mail.gmail.com>
Subject: Re: [CSV] CSVMutableRecord
To: Commons Users List <user@commons.apache.org>
Content-Type: multipart/alternative; boundary="94eb2c1fcd30b9aa860556cb385f"
archived-at: Tue, 15 Aug 2017 14:01:58 -0000

--94eb2c1fcd30b9aa860556cb385f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

How does that work when you want to change more than one value?

Gary

On Aug 15, 2017 00:17, "Benedikt Ritter" <britter@apache.org> wrote:

> Hi,
>
> I very much like that CSVRecord is unmodifiable. So I=E2=80=99d suggest a=
n API,
> that creates a new record instead of mutating the existing one:
>
> CSVRecord newRecord =3D myRecord.put(1, =E2=80=9Evalue")
>
> I=E2=80=99m not sure about =E2=80=9Eput=E2=80=9C as a method name since i=
t clashes with
> java.util.Map#put, which is mutation based...
>
> Regards,
> Benedikt
>
> > Am 15.08.2017 um 02:54 schrieb Gary Gregory <garydgregory@gmail.com>:
> >
> > Feel free to provide a PR on GitHub :-)
> >
> > Gary
> >
> > On Aug 14, 2017 15:29, "Gary Gregory" <garydgregory@gmail.com> wrote:
> >
> >> I think we've kept the design as YAGNI as possible... :-)
> >>
> >> Gary
> >>
> >> On Mon, Aug 14, 2017 at 3:25 PM, nitin mahendru <
> >> nitin.mahendru88@gmail.com> wrote:
> >>
> >>> Yeah that also is OK. I though there is a reason to keep the CSVRecor=
d
> >>> without setters. But maybe not!
> >>>
> >>> Nitin
> >>>
> >>>
> >>>
> >>>
> >>> On Mon, Aug 14, 2017 at 2:22 PM Gary Gregory <garydgregory@gmail.com>
> >>> wrote:
> >>>
> >>>> Hi All:
> >>>>
> >>>> Should we consider adding put(int,Object) and put(String, Object) to
> the
> >>>> current CSVRecord class?
> >>>>
> >>>> Gary
> >>>>
> >>>> On Mon, Aug 14, 2017 at 2:54 PM, nitin mahendru <
> >>>> nitin.mahendru88@gmail.com>
> >>>> wrote:
> >>>>
> >>>>> Hi Everyone,
> >>>>>
> >>>>> I recently pushed a change(pull request 20) to get the line ending
> >>> from
> >>>> the
> >>>>> parser.
> >>>>>
> >>>>> Now I want to push another change which I feel will also be useful
> for
> >>>> the
> >>>>> community. I want to add a CSVRecordMutable class which had a
> >>> constructor
> >>>>> which accepts a CSVRecord object. So when we have a CSVRecordMutabl=
e
> >>>> object
> >>>>> from it then we can edit individual columns using it.
> >>>>>
> >>>>> I would be using this to write back my edited CSV file. My use case
> >>> is to
> >>>>> read a csv, mangle some columns, write back a new csv.
> >>>>>
> >>>>> I could have directly raised a pull request but I just wanted to
> float
> >>>> the
> >>>>> idea before and see the reaction.
> >>>>>
> >>>>> Thanks
> >>>>>
> >>>>> Nitin
> >>>>>
> >>>>
> >>>
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
> For additional commands, e-mail: user-help@commons.apache.org
>
>

--94eb2c1fcd30b9aa860556cb385f--