2020 LinuxQuestions.org Members Choice AwardsThis forum is for the 2020 LinuxQuestions.org Members Choice Awards.
You can now vote for your favorite projects/products of 2020. This is your chance to be heard! Voting ends on February 17th.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It also has the worst defaults of all databases I ever worked with, making it extremely hard to migrate existing databases from Windows to Linux or HP-UX.
I'm struggling to understand how defaults relate to migration (sql_mode?). Do you have time to provide me with more details? Which source databases do you consider here?
Quote:
Originally Posted by Tux!
It also has the worst possible user-management options, which makes me stay away from it as long as possible. dbeaver helps, but still.
Other notable user-management options that have existed for a while, that can easily get missed are: account locking was added in 10.4.2 and password expiry in 10.4.3. The SUPER privilege was split up in 10.5.2.
With these it looks almost comparable to Postgres in terms of user management features. Or have I missed a key feature that still is required?
I'm struggling to understand how defaults relate to migration (sql_mode?). Do you have time to provide me with more details? Which source databases do you consider here?
1. On windows file names are case insensative and tables are created the way the user used capitalisation on typing the "create table" SQL command. I've seen more than once that migration to file systems that are not case insensative will FAIL on the ANSI standard the typing table names in SQL commands is ought to be case insensative does not work. Likewise for compiled programs that use all lowercase vs all uppercase in SQL commands.
2. The default installation for mysql was (and I fear still is) prohibits spaces on places that will make end users curse: "select count (*) from foo;" is (was) not allowed in a default installation. (a space between count and (*)). This is for all functions.
So I need to add two lines to /etc/my.cnf to be able to work with MySQL/MariaDB at all
Other notable user-management options that have existed for a while, that can easily get missed are: account locking was added in 10.4.2 and password expiry in 10.4.3. The SUPER privilege was split up in 10.5.2.
With these it looks almost comparable to Postgres in terms of user management features. Or have I missed a key feature that still is required?
I *LOVE* DBeaver! It takes away most of my user-management issues for MySQL and Oracle.
Thanks for the extra links, I'm going to store them in my mysql notes
For embedded systems, SQLite is hard to beat. If actual database servers are involved, PostgreSQL is the clear winner in terms of features, scalability, price (sorry Oracle) and performance. I'll choose PostgreSQL because it's what I use the most right now.
PostgreSQL and performance in one sentence? Very cool. Performance is better than in 9.X versions, but query optimizer is still pretty primitive, at least compared to MS SQL Server. On SQL Server I write my query however and it's fast. On PostgreSQL - write however and it's slow, so then google, ask around for every trick imaginable - way faster than initial quickly written query, still slower than SQL Server.
Blah, meant to say arm64 support. And armhf/armel are packaged by Debian and others.
Not all ARMv8 (Aarch64) are created equal. All currently supported MariaDB server releases should work on the Raspberry Pi. Early 10.5 releases crashed on 64-bit Raspberry Pi models, but that was addressed by https://github.com/MariaDB/server/pull/1645.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.