Re: Copy/Paste table(s) functions - git context patch

I do not know what happened, but I am quite sure that it is not a
frmPasteObject.cpp!

1. Copy operations are in a new thread (the GUI is not blocked)
2. Copy operations do not use the GUI objects
3, Source objects are on a new connection (does not affect the status
of the browser)
4. Target objects are on a new connection (does not affect the status
of the browser)

On 7/17/11, Guillaume Lelarge <guillaume(at)lelarge(dot)info> wrote:
> On Sat, 2011-07-16 at 15:45 +0200, Vladimir Kokovic wrote:
>> Hi,
>>
>> Again, patch for Copy/Paste table(s) functions.
>>
>> Done the following:
>> 1. Copy table/schema in the same schema
>> 2. Thread implementation for copy table(s) operations
>>
>
> There's a really big bug (as in "segfault bug"). Try to copy a big table
> (I did it with a 5,000,000 rows, 248MB table), and while doing the copy,
> try to create a schema in the same database (it could have the same
> effect with other objects, but I didn't try that). It just crashes. The
> schema is available, but the new table isn't.
>
> I wonder why you need a frmPasteObject at all. For the new thread? well,
> anyway, if you have a frm*, it should display something. And I think it
> would be great to actually show a list of objects that will be copied
> and show the progress (as in "this table done, this table done, etc.").
>
> Now that we can copy on the same schema, it shouldn't ask for an
> extension, but for the complete name.
>
>
> --
> Guillaume
> http://blog.guillaume.lelarge.info
> http://www.dalibo.com
>
>