I'm trying to install Magento Community Edition for my latest project on our server, however, the hosting platform we are currently using doesn't, and won't let us, install or utilise InnoDB.
Is anyone aware of any configuration/changes that can be done to make it work any other way?
Magento was developed and is supposed to be used in a transaction-safe environment.
You could try switching to some other database which is transaction-safe (like Oracle), but then you'd need to write PDO adapters and resource models for Oracle by yourself (they're not part of Magento). But if your provider doesn't even support InnoDB, I don't believe he will support Oracle or similiar^^
Another possibility would be to make Magento able to work with a non-transactional mySQL engine like MyISAM. You'd need to rewrite many processes, core models and controllers to change Magento from transactional to non-transactional behaviour.
Not only would this be tons of work, but I'm almost sure, you would get a lot of fun each time you try to upgrade your Magento version. I'd strongly encourage to never change the core this way.
The only mySQL engines supporting transactions are InnoDB and NDB. Magento only ships resource models for InnoDB. So, if you ask me, if your provider doesn't allow InnoDB for whatever reasons, I'd recommend to just move on to another provider that does.
I was trying to install Magento 1.9 CE on my own development server. Eventually the Magento Downloader incorrectly stated that InnoDB is not the default database engine. This was the issue I had when installing Magento CE.
Yes, it is true that MariaDB, a binary compatible replacement for MySQL uses xtradb rather than innodb as its engine.
https://mariadb.com/kb/en/mariadb/xtradb-and-innodb/
However, I am tempted to conclude the problem lies in Magento:
Magento install complains about missing InnoDB when it is available
Related
I understand that the Plugin is available for Enterprise MySQL only. However it is also available as a open source under MariaDB. I am trying to implement column level encryption on my MySQL 8.0.23 over AWS EC2. Can someone let me know if this possible, or is there any other open source plugin from Percona which gives the same functionality. Please help with the link to directly download the such plugin if available.
I need to know if there are any other ways of having column level encryption on MySQL Community edition. This need to be implemented from database only not from the application end.
The encryption on the underlying MariaDB, and I assume MySQL is the same way that applies on the table level. InnoDB pages are read from disk and decrypted. This is the lowest level of functional encryption/decryption.
Options with existing encryption are:
Put your encrypted column in its own table and join to it
Encrypt the entire table
I searched alot to install python3.6 and django2.0.2 with MySql server, but I got nothing because django2.0.2 framework doesn't support MySqldb yet.
Django REST Framework does support MySQL engine.
Django supports MySQL 5.5 and higher.
Django’s inspectdb feature uses the information_schema database, which
contains detailed data on all database schemas.
Django expects the database to support Unicode (UTF-8 encoding) and
delegates to it the task of enforcing transactions and referential
integrity. It is important to be aware of the fact that the two latter
ones aren’t actually enforced by MySQL when using the MyISAM storage
engine, see the next section.
Source: https://docs.djangoproject.com/en/2.0/ref/databases/
Follow the link to setup the configuration
Does Phinx support pt-online-schema-change?
I realize Phinx is supposed to handle DB migrations. But in the live environment, running a simple ALTER TABLE command on a huge table might lead to a table lock and temporary service unavailability.
There is a tool from Percona Toolkit called pt-online-schema-change which can handle the schema migration without any downtime, by creating a temporary table, copying the data and re-applying the log.
Is there a way to easily integrate these two, in order to get nice DB migration management from Phinx, and the production zero downtime from Percona Toolkit? Is there any other DB migration management tool, which supports pt-online-schema-change?
Phinx doesn't support 'pt-online-schema-change' at the moment. You could try opening an issue on the Github project for future support (if it proves to be popular). Somebody has been hacking on something similar (see: https://github.com/masom/lhm_php). It is a port of a ruby-based SoundCloud project.
I would like to replace MySQL 5.1 on my Debian Lenny 32-bit server to Percona Server with XtraDB. The main reason is better performance of Percona.
It's production server with many services running. Many other software may depend on mysql-client and other mysql shared libraries.
Is it safe to replace MySQL?
By "safe" I mean: 1. remove mysql, 2. install percona 3. everything works as before
Will it break dependencies in third party software?
Will it require to change configuration of third party software (ie. socket path, server port, shared libraries path)?
Will it require to install trillion of additional packages?
I really don't want situation with broken libraries, missing or incompatible header files and so on
We are currently in the process of upgrading from MySQL 4.1 to Percona Server 5.5 at work and Percona is as they say on their site a complete drop-in replacement for MySQL, the binaries use the same names, it uses the same libraries, same config file placement, takes the same parameters and it has exactly the same SQL syntax. They should also be data file compatible on the same version (MySQL 5.1 to Percona 5.1, etc) but it's nothing I've personally verified.
You are able to do an apt-get install percona-server-server-5.1 after adding their repositiories and it will automatically replace MySQL because it marks it as a conflicting package. But you must take an SQL dump of your database first, of course.
We currently have replication set up from a MySQL 4.1 master to a couple of Percona 5.5 slaves and have had no problems inserting SQL dumps either.
... don't know.
In my experience, the only way is to make up a copy of your existing setup on an old machine and run some tests. Then swap over to the new DB and run same tests again.
I just swapped a set of applications from Tomcat 5 to Tomcat 6 and in theory, with one or two tweaks, all should have worked fine. First time I tried it OpenJava was installed and the garbage collection fouled things up. Second time around with Sun Java, some dodgy date handling fouled things up and had to be corrected, seems to run fine now.
I'm using a rather busy MySQL 5.0 database. What are the main reasons for me to migrate to MySQL 5.1? Does it worth the trouble?
I use VS2008/.NET 3.5
Servers run as a MySQL cluster on Windows 2008 servers.
Thank you for your answers so far. To be more specific - I'm looking for answers such as the one by Quanssnoi, listing the features most important to him, rather than links to MySQL feature lists, which I of course read. Thanks.
Top reasons for me would be partitioning and XPath support.
For me the most important new feature was row-based replication.
Here's a list of new features in MySQL 5.1: What's New in MySQL 5.1 If you're not going to take advantage of these new features, and you have a production system running on MySQL 5.0, then moving to MySQL 5.1 might not be worth the trouble.
MySQL 6.0 (which is still in Alpha stage), on the other hand, brings a slew of new features including utf16 and utf32 support, and a new storage engine called Falcon.
I've noticed that DB dumps and loading of dumps works much better in 5.1 (5.0 has issues with those backwards compatibility comments). Notice I'm not referring to schema Backup, but dumps (different things).