I'm not a fan of MySQL, which perhaps explains why I didn't know about MariaDB, but I know a lot of people use MySQL, so they may find this of interest. MariaDB is a a true open source fork of MySQL that's supposed to be a drop-in replacement for it.
I'm not a fan of MySQL, which perhaps explains why I didn't know about MariaDB, but I know a lot of people use MySQL, so they may find this of interest. MariaDB is a a true open source fork of MySQL that's supposed to be a drop-in replacement for it.
https://mariadb.org/
https://mariadb.org/
Why don't you like MySQL? I've been using it daily for multiple, large corporate apps and it hasn't skipped a beat. I've used Zeos, and DevArt MyDAC on Delphi and the standard MySQL libs on PHP. Zero issues in 7 years.
ReplyDeleteI guess you're lucky, or I'm unlucky, but prior to swearing off MySQL, I had experienced multiple data corruption events across different installations, with different clients, and scenarios. There were also a bunch of well-documented "gotchas" with MySQL that I found quite annoying, though I don't recall them now.
ReplyDeleteI think it was around v4.1 - 5.0, before the Sun, then Oracle, acquisitions that I gave up on MySQL, but it may have improved over time. I've been with PostgreSQL ever since and it's been rock-solid. I have no regrets about switching and no plans to ever switch back.
Kevin Powick Are you sure it wasn't a flaky server? I've been using commercial server hardware here at the day-job, but I also use MySQL for hobby projects at home on a standard tower PC server. Could also be flaky SQL code :-) gd,r
ReplyDeleteKevin McCoy Positive. Multiple different customers, servers, and use case scenarios. MySQL may work well for many, but I certainly wasn't alone with the problems I experienced. While I'm fully aware that no database is perfect, my experience with PostgreSQL is like yours with MySQL, no problems, ever. :-)
ReplyDeleteI use MariaDB for a while. It works as expected and does what they say. It's very solid, binary compatible, even the excutable and library name files are the same. Use the same configuration file, same option for the common db engines. If you follow the conventions it works very fine. I use both, server and embeded with ZeosLib 7, since Delphi 7!
ReplyDeletePostgres is awesome. MySQL is meh.
ReplyDeleteMariaDB begins from a branch of MYSQL. actually , they are the same , in some way.
ReplyDeleteLooks like Wikipedia is dumping MySQL for MariaDB
ReplyDeletehttp://www.infoworld.com/t/open-source-software/wikipedia-dumps-mysql-hooks-mariadb-217820
Kevin Powick Interesting! I don't have a dog in the Sun/Oracle fight, but a pure open-source project that is a drop in replacement for MySQL sounds intriguing. I have several mega-lines of Delphi code dependent on MySQL.
ReplyDeleteKevin McCoy you are fine if you go all the way with MariaDB. There's no difference at all you can see. It's fully compatible and has the advantage to be a real open source. It's rock solid in all my test, even faster. Also you have access to other db engines like Aria.
ReplyDeleteI am not using that MySQL version, but when I tried your test in the Query Browser, it successfully created the table. When I added the partial record an error occurred. No partial record was added (as would be expected).
ReplyDeleteGraeme Geldenhuys
ReplyDeleteI think most of your problem is that you are using the command line utility to manipulate MySQL tables. The GUI query browser won't allow you do any of that foolishness. :-) It forces all table names to lower case and rolls back any erroneous insert transactions (as your code should do as well).
Graeme Geldenhuys
ReplyDeleteI don't think a low level tool like the MySQL command line utility or even the GUI Query Browser can be compared with a functioning DB app. Both tools designed to do low level housekeeping chores on a MySQL DB that should not be done in production code. Give me a few days with any DB engine and I will break it for you :-)
Graeme Geldenhuys I think your last reply was intended for Kevin McCoy ?
ReplyDelete