> -w, --where=nameDump only selected records; QUOTES mandatory!
>
> :)
The more options the merrier for MySQL and the end-users :)
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
"SciBit MySQL Team" <[EMAIL PROTECTED]> wrote:
> select * from accounts; -- as an example
>
> but because you can customize the source sql script for MyRun, you can go like:
>
> select * from accounts where AccountDate>YEAR(CURDATE()); --
>
> i.e. limit the inserts you going to get to that whic
> Great, MyCon produces "SQL statements ready to recreate just your schema and/or all
> data as well", now did I miss something, or does MyCon actually write the SQL one
> needs to create and populate a set of system tables for the schema?
>
> PB
> .
Nope Peter, you didn't miss a beat ;)
Jus
> mysqldump --no-data --all-databases
>
>
> Eamon Daly
Yeap Eamon, as mentioned MyRun is not the only utility on earth with the
functionality. The difference between mysqldump and MyRun is that while MyRun
includes all the mysqldump
" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, August 11, 2004 4:34 PM
Subject: RE: Re: [OT] PostgreSQL / MySQL Data Dictionary
> > In MySQL, by parsing the output of SHOW CREATE TABLE.
> >
> > It would be a boon if someone were to write a utility,
> In MySQL, by parsing the output of SHOW CREATE TABLE.
>
> It would be a boon if someone were to write a utility, in an OS-independent
> language, which does that parsing for all tables in a MySQL database and
> returns SQL output that's suitable for creating a set of system tables.
> Obviously
> SHOW TABLES does not make sense. How are you going to join the
> output of SHOW TABLES against the output of SHOW COLUMNS and
> SHOW INDEXES?
In MySQL, by parsing the output of SHOW CREATE TABLE.
It would be a boon if someone were to write a utility, in an OS-independent
language, which does th
On Wed, 11 Aug 2004 11:04:01 -0500, Josh Trutwin wrote:
> On Wed, 11 Aug 2004 17:20:45 +0200 Jochem van Dieten wrote:
>>
>> SHOW TABLES does not make sense. How are you going to join the
>> output of SHOW TABLES against the output of SHOW COLUMNS and SHOW
>> INDEXES?
>>
>> SELECT * FROM INFORMATIO
On Wed, 11 Aug 2004 17:20:45 +0200
Jochem van Dieten <[EMAIL PROTECTED]> wrote:
> SHOW TABLES does not make sense. How are you going to join the
> output of SHOW TABLES against the output of SHOW COLUMNS and SHOW
> INDEXES?
>
> SELECT * FROM INFORMATION_SCHEMA.TABLES makes sense.
>
>
> And as f
