Register

If this is your first visit, please click the Sign Up now button to begin the process of creating your account so you can begin posting on our forums! The Sign Up process will only take up about a minute of two of your time.

Results 1 to 10 of 10

Thread: MySQL-Max

  1. #1
    Senior Member ubunreal's Avatar
    Join Date
    Apr 2002
    Location
    Brisbane
    Posts
    263
    Member #
    62
    MySQL-Max - MySQL version with two table handlers (InnoDB & BDB), that provide transactions to MySQL.
    whats the difference with InnoDB & BDB ? (and what are they ?)

  2.  

  3. #2
    Guest
    innoDB = Innobase

    InnoDB is a table type in MySQL.
    See here for advantages of using innodb type.

    BDB = Berkley Database Base or for your definition Berkley Database Base Tables

    Again it's a table type in mysql.
    Sorry no link!

    Umm some differences are:

    BDB = page-level locking and is slower than MyISAM
    InnoDB = row-level locking, multi-versioning, newer

  4. #3
    Senior Member ubunreal's Avatar
    Join Date
    Apr 2002
    Location
    Brisbane
    Posts
    263
    Member #
    62
    still after reading that ionfo dont understand wha tis so usefull aboutu InnoDB (I'm not a DB man)

  5. #4
    Guest
    Keh?
    I listed the advantages:

    InnoDB tables are transactional: they provide rollback and commit capabilities.
    InnoDB is the only table type in MySQL which supports foreign key constraints.
    InnoDB tables are fast, even faster than MyISAM tables in many simple benchmarks. See the benchmark page.
    InnoDB tables have row level locking: they allow higher concurrency than MyISAM tables which use table level locking, or BDB tables, which use page level locking. High concurrency is reflected in high multiuser performance.
    InnoDB tables provide an Oracle-style consistent read, also known as multiversioned concurrency control. SELECTs do not need to set any locks and need not interfere with inserts and updates to the same table. No other MySQL table type has this property.
    There is a true hot backup tool available for InnoDB, which allows you to make backups of a running database in background, without setting any locks or disturbing database operation.
    Multiversioning also allows you to dump tables from your database with SELECT INTO OUTFILE without setting locks on the tables: the database can keep working while a backup is made.
    InnoDB tables have automatic crash recovery. You do not need to repair your tables if the operating system or the database server crashes, when there is no disk image corruption.
    InnoDB tables can be any size, also on those operating systems where file size is restricted to < 2 GB.

  6. #5
    Senior Member ubunreal's Avatar
    Join Date
    Apr 2002
    Location
    Brisbane
    Posts
    263
    Member #
    62
    Originally posted by beacon
    Keh?
    I listed the advantages:

    InnoDB tables are transactional: they provide rollback and commit capabilities.
    InnoDB is the only table type in MySQL which supports foreign key constraints.
    InnoDB tables are fast, even faster than MyISAM tables in many simple benchmarks. See the benchmark page.
    InnoDB tables have row level locking: they allow higher concurrency than MyISAM tables which use table level locking, or BDB tables, which use page level locking. High concurrency is reflected in high multiuser performance.
    InnoDB tables provide an Oracle-style consistent read, also known as multiversioned concurrency control. SELECTs do not need to set any locks and need not interfere with inserts and updates to the same table. No other MySQL table type has this property.
    There is a true hot backup tool available for InnoDB, which allows you to make backups of a running database in background, without setting any locks or disturbing database operation.
    Multiversioning also allows you to dump tables from your database with SELECT INTO OUTFILE without setting locks on the tables: the database can keep working while a backup is made.
    InnoDB tables have automatic crash recovery. You do not need to repair your tables if the operating system or the database server crashes, when there is no disk image corruption.
    InnoDB tables can be any size, also on those operating systems where file size is restricted to < 2 GB.
    rollback and commit capabilities.
    ??

    InnoDB is the only table type in MySQL which supports foreign key constraints.
    ??

    c what i mean ?

  7. #6
    Guest
    Ohh ok:

    rollback = like undo kinda.
    commit = make changes commit the changes.
    etc etc.

    Umm a better way:
    Innodb = basically is better for lots of concurrent users and concurrent data changes.

  8. #7
    Senior Member ubunreal's Avatar
    Join Date
    Apr 2002
    Location
    Brisbane
    Posts
    263
    Member #
    62
    umm, gebberish dude dont worry bout it. i dont really need to know this stuff, i was just curious, thats all

  9. #8
    Guest
    Umm ok:

    Innodb = Fast and can handle more users.


    Sorry

  10. #9
    Senior Member ubunreal's Avatar
    Join Date
    Apr 2002
    Location
    Brisbane
    Posts
    263
    Member #
    62
    ooook, so its just like a better method of MySQL to create tables that makes them faster / support more users sinultaneously ?

  11. #10
    Guest
    Yup then other types of tables!
    Not just that but thats the basics.


Remove Ads

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
All times are GMT -6. The time now is 11:19 AM.
Powered by vBulletin® Version 4.2.3
Copyright © 2019 vBulletin Solutions, Inc. All rights reserved.
vBulletin Skin By: PurevB.com