Re: Importing tables w/large initial extents into a small database

Joel Garry wrote:
>

<snip>
> An excellent suggestion, except for the fact the resulting log file requires
> a whole lot of manual intervention. The resulting file has line breaks in
> all sorts of weird places, and no easy way to know when the next line is
> supposed to begin. In other words, you can't just put a ; at the end of
> each line, substitute DROP for ^TABLE and have a sql file. The one I just
> tried, had stuff like the end of line being VARCHA" and the beginning of
> the next line like "R2(30), (with quotes and comma).
>

Yeah, it's realy a pain... and that's the reason why i keep the create-script of
the DB's.  

<snip>  

> Thank you for pointing out that I wasn't too clear about not editing actual
> export files that will be used in the future with import. That was what
> I meant by brave and careful. Work on a copy.
>

And i thought i was brave, when i changed the files without any backup-copy ;-)

eugen Received on Wed May 13 1998 - 12:20:33 CDT