![]() Somewhere in phpmyadmin, it connects using mysqli, just like the php systems I made. some of this is out of sequence, because something else stopped working and there was no way I was going to have to go through all my code to make everything comply with strict sql_mode, and fortunately God loves me, which I know, because it took only a minute to add a line to the php-sql module I wrote and is used by ALL the sql in my system, which I was sure wouild make me world famous and rich someday, so that right after a connection is made to a database, a simple command sets the sql_mode to the non strict mode and life is good again, even though I have bypassed the protection so generously delivered by mariadb to my ignorant old fashioned and not rich world. it didn't care that every field had a default value applied to it when the php application added records, I could not just add the field and say save. It happened the table I was trying to change, probably add a field. it was because strict mode said it was not good enough to fail to provide explicit default values for every field whereas before that was fine. Ok, it only took a few hours to figure out why I was getting messages instead of data. don't answer that.Īs everyone knows, because everyone got the memo and everyone agreed on the night I went to sleep early, mariadb defaults sql_mode to strict, starting a few versions ago. Mariadb helps me by defaulting to a sql_mode, something I did not know had options, yes I want sql mode.I have to say what kind of sql mode? Why? What kinds are there. I love things that are put into my life against my will, that are mandatory because they help in ways I don't know I need. I don't know why Debian and LAMP started showing up with Mariadb instead Mysql, but I do know a lot of agony was avoided thanks to MariaDB and MySQL both starting with the third letter in LAMP. Then some people with vision and skills I lack took it upon themselves to develop for the benefit of humanity and cost to themselves a fork from mysql, and I probably have it wrong, I think that is something like how we got MariaDB. ![]() I knew that was bad, but all in all, time has proven the fears I had when oracle bought mysql have not materialized. Mysql was FREE, a serious DB, not a toy and not encumbered by any of those intricate iron boxes with weird connectors that Microsoft uses to make their systems interconnect and simultaneously, very difficult to integrate. Microsoft SQL SERVER was dirt cheap and thanks to having most of what it did developed by engineers not at micosoft, from whom Microsoft had bought it, and before Microsoft entombed it inside its layers of technology that simplified it by making it almost impossible to work with, for the low low low price of only a few hundred dollars provided you did not deploy it on too big a system but it wasn't FREE. Some years went by, imagine my surprise to discover mysql FREE, doing everything I ever heard of wanting to do with Oracle, only it was FREE. The only barrier I encounted was the software licence fee, less than $20,000 as I recall, but anything over $1,000 was probably next to impossible for me. When I started out in this line of work, I wanted to get a copy of Oracle, which at that time was a word that meant "serious relational database, not a toy," on my computer so I could see it and someday get paid for being able to run it. When I remove the "WITH mysql_native_password" part from the query it executes just fine.Mysql is one of the best things that ever happened to me. I don't really know why phpMyAdmin explicitly names the authentication plugin/mechanism when it's using the default and only installed MySQL native password. ![]() The syntax highlighting complains about the with in "WITH mysql_native_password" and about the word "USAGE" in the GRANT statement. The full query as created by phpMyAdmin looks like this: CREATE USER IDENTIFIED WITH mysql_native_password BY '***' GRANT USAGE ON *.* TO REQUIRE NONE WITH MAX_QUERIES_PER_HOUR 0 MAX_CONNECTIONS_PER_HOUR 0 MAX_UPDATES_PER_HOUR 0 MAX_USER_CONNECTIONS 0 When trying to create a new user in phpMyAdmin 4.5.0 on a MariaDB database I get a "1065 - Query was empty" error above the printed query and "The selected user was not found in the privilege table." right on top of the user creation wizard.Īlso when I try to edit the query inline, the highlighting complains about an unrecognized statement type "WITH".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |