We're just gonna have to call .schema for the original table and use that to make repeated addColumnDefinition calls on the target table. That help?
--tim On Sunday, August 24, 2014, Chris Rohr <[email protected]> wrote: > Ok, so this is going to sound really noob but I don't know how to add > the column defs and the docs don't seem to have anything, unless the > process is to run a bunch of mutates. > > Sorry for the simple question, but this could be a good docs update. :-) > > On Sun, Aug 24, 2014 at 12:03 PM, Chris Rohr <[email protected] > <javascript:;>> wrote: > > I can try if you want, I found it because I'm adding the same > functionality > > to the console. > > > > > > On Sunday, August 24, 2014, Tim Williams <[email protected] > <javascript:;>> wrote: > >> > >> The goal should be to copy the schema too - I think I just forgot to add > >> the column defs to it. I can add that in if no one beats me to it.... > >> > >> --tim > >> > >> On Sunday, August 24, 2014, Chris Rohr <[email protected] > <javascript:;>> wrote: > >> > >> > Is the copy command supposed to copy the schema, or just create a new > >> > table? It seems like its just creating a new table, but the schema is > >> > not copying over. > >> > > >> > > >> > Thanks, > >> > Chris > >> > >
