Results 1 to 6 of 6

Thread: Any reason I should NOT use MySQL InnoDB?

  1. #1
    Johan van Zyl
    Guest

    Default Any reason I should NOT use MySQL InnoDB?

    Hi All

    Any reason I should NOT use MySQL InnoDB - as opposed to MyIsam, as I
    want to use Stored Procs, Triggers and Foreign Keys?

    (I would have preferred PostGreSQL, but hosting seems a problem)

    NOF9, site hosted by DreamHost.
    http://www.watzon.co.za

    --
    Johan van Zyl
    johan@jvz.co.za http://www.jvz.co.za
    johan@acctual.net http://www.acctual.co.za
    johan@watzon.co.za http://www.watzon.co.za
    079 549 0034 Cell/Mobile
    012 543 2919 Huis/Home
    086 622 9554 Fax
    Give a man a fish, and he eats for a day.
    Hit him with a fish, and he goes away for good!
    Teach a man how to surf the Internet and he will never bother you again.

  2. #2
    Johan van Zyl
    Guest

    Default Re: Any reason why I should NOT use MySQL InnoDB? - the future ofInnoDB

    InnoDB is transactional engine for MySQL; standard MySQL (MyISAM) tables
    are basically a flat file system with a SQL interface. Interestingly
    Oracle tried to buy MySQL, got turned down, but did succeed in buying
    InnoDB. That's raised a lot of questions about the future of InnoDB
    since it's some form of competition for Oracle. Oracle has said nothing
    will change.

    Apparently in response to the Oracle deal, the folks at MySQL have
    worked with Solid Information Technology to integrate SolidDB as a new
    transactional engine for MySQL. Solid's background is in phone systems,
    huge industrial databases. I really don't know the current status of
    SolidDB for MySQL.

    http://soliddb.com/pdfs/SolidDB_MySQL_DS.pdf
    http://www.clarionmag.com/cmag/v8/v8n07oscon5.html

    I've been a big fan of MySQL for many years, but I think this
    uncertainty about the transactional engine isn't doing them any good.
    Within a year I expect to retire my MySQL data in favor of PostgreSQL.
    re-posted from Clarion NG
    David Harms

    Johan van Zyl wrote:
    > Hi All
    >
    > Any reason I should NOT use MySQL InnoDB - as opposed to MyIsam, as I
    > want to use Stored Procs, Triggers and Foreign Keys?
    >
    > (I would have preferred PostGreSQL, but hosting seems a problem)
    >
    > NOF9, site hosted by DreamHost.
    > http://www.watzon.co.za
    >


    --
    Johan van Zyl
    johan@jvz.co.za http://www.jvz.co.za
    johan@acctual.net http://www.acctual.co.za
    johan@watzon.co.za http://www.watzon.co.za
    079 549 0034 Cell/Mobile
    012 543 2919 Huis/Home
    086 622 9554 Fax
    Give a man a fish, and he eats for a day.
    Hit him with a fish, and he goes away for good!
    Teach a man how to surf the Internet and he will never bother you again.

  3. #3
    Junior Member
    Join Date
    May 2015
    Posts
    13

    Default

    I'd go for Oracle, just for interoperability reasons.

  4. #4
    Junior Member
    Join Date
    Jan 2017
    Posts
    3

    Default Any reason I should NOT use MySQL InnoDB

    #10340 You do not have permission to view this topic.I get this when clicking on the game for the 1st april? dont you guys love me anymore?

  5. #5

    Default

    oracle bought MySQL InnoDB as of it's competition. i recommend not to use it.

  6. #6

    Default

    I recommend you to try Oracle.
    Last edited by ghostwriter; 01-18-2018 at 08:38 AM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •