oh, i didnt' know it's slow. yes in my case it's a way of transferring a row from one df to another. what's a better way of doing this?
On 12 September 2014 22:39, John Myles White <johnmyleswh...@gmail.com> wrote: > What does that mean? A DataFrameRow can't be easily created without > reference to an existing DataFrame, so this seems like it's either a > mechanism for transferring rows from one DataFrame to another very slowly > or a mechanism for inserting duplicate rows. > > -- John > > On Sep 12, 2014, at 3:37 PM, Florian Oswald <florian.osw...@gmail.com> > wrote: > > I'll submit a PR for Base.append!(adf::AbstracDataFrame,dfr::DataFrameRow) > unless you tell me that's useless. > > On 12 September 2014 22:31, Florian Oswald <florian.osw...@gmail.com> > wrote: > >> Leah: yeah that works. but i think i almost prefer my previous solution, >> instead of this push!(df2,[v for (_,v) in e]) >> that: >> push!(df2,array(e)) >> >> not sure about the performance implications though. >> >> >> >> >> On 12 September 2014 22:18, Gray Calhoun <gcalh...@iastate.edu> wrote: >> >>> Oh, I wasn't thinking of that. Good point. A mutating OrderedDict >>> constructor would allow reuse, but isn't as generic. >>> >> >> > >
