Re: Patch for mysqldump

[Stewart Smith]

Marco Gergele <marco....@gmail.com> writes:
> --limit[=name] (numeric!) Number of rows of each table to dump, 0=all
> rows
>
> I do need the number for "limit" as a string, so I try to avoid converting
> it into numbers and back into string.

The conversion is essentially free, so I wouldn't worry about the cost
of converting back and forth.
--
Stewart Smith

[Sveta Smirnova]

Hi Marco,

thank you for the patch!

Could you please open a feature request at bugs.mysql.com, put your
patch there and sign Oracle Contributor Agreement (OCA) as described in
newly created bug report in "Contributions" tab?

This will make possible for Oracle to accept this patch and include into
future versions.

Thank you,
Sveta.

On 05/05/2013 11:06 PM, Marco Gergele wrote:
> Hi,
>
> mysqldump can sort by primary key, but only ascending.
>
> mysqldump can not limit the number of rows.
>
> I have added two options:
>
> --order-by-primary-desc
> Sorts descending each table's rows by primary key, or
> first unique key, if such a key exists. Useful when
> dumping a MyISAM table to be loaded into an
> InnoDB table,
> but will make the dump itself take considerably
> longer.

>
> --limit[=name] (numeric!) Number of rows of each table to dump, 0=all
> rows
>
> I do need the number for "limit" as a string, so I try to avoid
> converting it into numbers and back into string.
>

> Greets - Marco Gergele
>
>
>
>

--
Sveta Smirnova, Principal Technical Support Engineer, Russia
MySQL @ Oracle, Moscow, Russia, www.oracle.com/mysql

--
MySQL Internals Mailing List
For list archives: http://lists.mysql.com/internals
To unsubscribe: http://lists.mysql.com/internals