List:General Discussion« Previous MessageNext Message »
From:SciBit MySQL Team Date:January 1 1970 12:00am
Subject:Re: [OT] PostgreSQL / MySQL Data Dictionary
View as plain text  
> PB
> .

Nope Peter, you didn't miss a beat ;)

Just to be very clear, MyCon is the front-end GUI which auto setup scripts for MyRun to
use for backups or it can also optionally schedule MyRun to auto execute these source
scripts.  The end-user hardly ever sees MyRun (except when the OS task scheduler fires it
up).  All the end-user ever does, is to click on a database (or a specific table) and
click Backup, the rest just "happens".  MyRun is the commandline utility which actually
does the hard yards. And to just state it again so there is no confusion; MyRun's target
script is fully capable of recreating the full schema as well as populate it with data
(insert statements) from whatever was selected in the source script.

NOTES:
* MyRun can also do this from a remote MySQL server.
* It can also execute the target script against another mysql server/database instead of
to a script file
* MySQL V3.23 and higher
* The target script can optionally contain "USE db;", "DROP table if exists tb1;", "CREATE
table if not exists tb1 ..." and your data using "INSERT into tb1 (..columns..) values
((...record1...),(...record2...),..);" in 100xrecord batches (so a 1,000 records will be
contained in only 10 insert statements).

These batch inserts are used because from the MySQL Manual: "This is much faster (many
times faster in some cases) than using separate single-row INSERT statements. If you are
adding data to non-empty table, you may tune up the bulk_insert_buffer_size variable to
make it even faster."

EXAMPLE:
Every morning we have a scheduled MyRun which backups up our company's MySQL webdata from
our remote webhost/ISP's MySQL server to our local network using a ADSL connection.  It
contains tens of tables with thousands of records each and from start to finish takes
approx. 10 seconds (our webhost and we are on different continents). And to set all this
up initially took a massive.. one click!

If our ISP drops our database by mistake, it will take us all of two seconds to recreate a
complete snapshot of the database using the latest target script.

Kind Regards
SciBit MySQL Team
http://www.scibit.com


Thread
Difference between PostgreSQL and MySQLEWAGW10 Aug
  • Re: Difference between PostgreSQL and MySQLBrad Tilley10 Aug
    • Re: Difference between PostgreSQL and MySQLJosh Trutwin10 Aug
      • Re: Difference between PostgreSQL and MySQLJochem van Dieten10 Aug
        • Re: Difference between PostgreSQL and MySQLJosh Trutwin11 Aug
          • Re: Difference between PostgreSQL and MySQLJochem van Dieten11 Aug
            • Re: [OT] PostgreSQL / MySQL Data DictionaryJosh Trutwin11 Aug
              • Re: [OT] PostgreSQL / MySQL Data DictionaryJochem van Dieten11 Aug
                • MySQL Data Dictionary (INFORMATION_SCHEMA)Jim Winstead11 Aug
                  • Re: MySQL Data Dictionary (INFORMATION_SCHEMA)Jochem van Dieten11 Aug
                  • Re: MySQL Data Dictionary (INFORMATION_SCHEMA)Josh Trutwin11 Aug
          • Changing Fulltext defaults in Win32leegold11 Aug
  • Re: Difference between PostgreSQL and MySQLJochem van Dieten10 Aug
  • Re: Difference between PostgreSQL and MySQLEWAGW10 Aug
  • Re: Difference between PostgreSQL and MySQLSGreen10 Aug
    • Re: Difference between PostgreSQL and MySQLMartijn Tonies10 Aug
    • Re: Difference between PostgreSQL and MySQLJochem van Dieten10 Aug
      • Re: Difference between PostgreSQL and MySQLJosh Trutwin11 Aug
  • Re: Difference between PostgreSQL and MySQLMartijn Tonies10 Aug
  • Re: Difference between PostgreSQL and MySQLEWAGW10 Aug
  • Re: Difference between PostgreSQL and MySQLEWAGW10 Aug
  • Re: Difference between PostgreSQL and MySQLEWAGW10 Aug
  • Re: Difference between PostgreSQL and MySQLmos11 Aug
    • RE: Difference between PostgreSQL and MySQLLachlan Mulcahy11 Aug
      • On the licensing once againDebugasRu11 Aug
        • Re: On the licensing once againZak Greant11 Aug
        • RE: On the licensing once againLachlan Mulcahy11 Aug
          • R: On the licensing once againLeonardo Francalanci11 Aug
            • Re: R: On the licensing once againDebugasRu11 Aug
              • RE: R: On the licensing once againLachlan Mulcahy11 Aug
          • Re: On the licensing once againIssac Goldstand12 Aug
            • Re: On the licensing once againZak Greant12 Aug
  • Converting access to mysql dbEWAGW11 Aug
  • Re: Changing Fulltext defaults in Win32Cemal Dalar11 Aug
    • Re: Changing Fulltext defaults in Win32leegold11 Aug
  • Re: Changing Fulltext defaults in Win32Cemal Dalar11 Aug
  • Re: [OT] PostgreSQL / MySQL Data DictionaryPeter  Brawley11 Aug
    • RE: Re: [OT] PostgreSQL / MySQL Data DictionarySciBit MySQL Team11 Aug
      • Re: [OT] PostgreSQL / MySQL Data DictionaryEamon Daly11 Aug
        • RE: Re: [OT] PostgreSQL / MySQL Data DictionarySciBit MySQL Team12 Aug
          • Re: [OT] PostgreSQL / MySQL Data DictionaryEgor Egorov12 Aug
            • RE: [OT] PostgreSQL / MySQL Data DictionarySciBit MySQL Team12 Aug
Re: On the licensing once againZak Greant11 Aug
Re: On the licensing once againLachlan Mulcahy11 Aug
  • R: On the licensing once againLeonardo Francalanci11 Aug
    • Re: R: On the licensing once againSantino11 Aug
      • Re: R: On the licensing once againZak Greant12 Aug
    • Re: R: On the licensing once againZak Greant12 Aug
Re: On the licensing once againLeonardo Francalanci11 Aug
  • Re: On the licensing once againRich Lafferty11 Aug
Re: [OT] PostgreSQL / MySQL Data DictionarySciBit MySQL Team12 Aug