I am requested to support a legacy system. I needed to install PHP4 on my computer for that and also MySQL 4.x. I couldn't find a MySQL 4.x version that installs on my computer so I thought I'd upgrade the system to MySQL 5.x. The problem is, PHP4 does not seem to work with MySQL 5.x.
I've read somewhere that something called mysqli is needed in PHP for it to be able to work with MySQL 5.x. I just couldn't quite understand whether it's something that is included in PHP5 or something I can add to PHP4.
If it's something I can add to PHP4, how?
Thanks.
PHP4 should work mostly fine with MySQL 5. Note I'm just talking from experience, sometimes it seems the technical stuff I read on the official MySQL and PHP sites have conflicted with what I observe. For what I've done, the only thing I really needed to worry about for compatibility between the two is authentication. Make sure the MySQL account you're trying to connect with from PHP4 uses the old password encoding. You can see this yourself in the mySQL user table. I can't remember the exact numbers but passwords stored under the old format are around 16 characters hashed whereas under the new format they are significantly longer.
More info here:
http://dev.mysql.com/doc/refman/5.5/en/old-client.html
Related
Currently we are using microstrategy as a reporting tool 11.1 version and using Oracle DB - micro strategy metadata, Statistics , history all installed in Oracle
now we are planning to move Db from Oracle to Postgres. just wanted to check if microstrategy support Potgres DB
Here is the list of certified and supported versions: Repositories
From personal experience I can say PostgreSQL v9,v10 and v11 runs fine as metadata repository. Tested v9-v12 as DWH too, all working without problems.
As far as I remember they didn't deliver the bundled driver in one of the MSTR-versions (2019-something), but that seems to have changed in MSTR-2020 again. Not a showstopper, but something to be aware of.
I am also running PG-11 as repo for History List too, but you definitely won't get help from support for this. OT: They even made me switch from MariaDB to MySQL for a support case (don't really blame them though, it's not certified and that's that).
My last attempt at running Statistics-Repo with PG is a long while ago and it didn't really work out of the box. Don't know what the situation is there. You might have to consider moving to PlatformAnalytics and/or MySQL(/MariaDB) for this too. EM only receives bugfixes from MSTR-2020 onwards, so this seems to be future-proof (EM discontinued from 2020 onwards?)
This mostly reflects our experience, the only certified PG version for MSTR 11.1 is PG-9 and only for the MD-Repo!
I've been tasked with upgrading our Postgresql database to 9.4 and I'm following the instructions found on the documentation found here:
Upgrading Postgresql
The second step for upgrading to 9.4 says this:
For source installs, build the new version
Build the new PostgreSQL source with configure flags that are compatible
with the old cluster. pg_upgrade will check pg_controldata to make sure all settings
are compatible before starting the upgrade.
I rarely have to go into the internals of PGSQL and I'm not sure what is meant by the term 'configure flags'. Is this a specfic term in reference to PGSQL or does this refer tot he command line options at the top of the documentation page? In fact, do I even need to do this? The very nex st sentence says that pg_ugprade will do it for me. I'm upgrading our database that has a lot of sensitive data and I need to get this right. Obviously I have a sandbox though to play with but if someone can help me understand what that means, I'd appreciate it. I've come to find that dealing with PGSQL can be frustrating as hell. Thanks.
I am using the trial version of the Zend Server edition. From all the videos/documentation supposedly you are able to change the database version from SQLITE to MySQL, but all I get when deploying an application on Zend Server is to set the Host, Database name, username and password?
Just install mysql on your system and use it. ZendServer does not care what database engine you use. When installing Zend Server it is supposed to ask if you want to install mysql (possibly you have to chose manual installation or custom or extra stuff) you might of mised that option so perhapds reinstalling is the simpler solution.
But really, you should be able to just install mysql and start using it.
Does PHP 4.4.8 version support mysqli object-oriented style? I have made ready this project on PHP5 and when I got online hosting, I came to know that the online version is 4.4.8.
How can I make my mysqli project work on this domain?
According to wikipedia, everything below PHP 5.2.17 (inclusively) is not supported any more (read: from PHP's point of view, it's history).
Thus you should urge your hosting company to upgrade. Use this argument. If they don't understand, they're not professional and you should change your hosting.
When you start using PHP 5.3, and if it's not too much effort, switch over to PDO.
Try writing a mysqli-compliant wrapper around the mysql_* functions.
Either that, or refactor your project to either use mysql_* your own db library.
I'm currently trying to set up some simple migration scripts for our databases. I was checking flyway, which seems to be simple enough for what I need. My problem is that, for Postgres, only version 9 is supported (we're using 8.4). Is it possible to work around/fix this limitation somehow, or should I start looking for other options?
Edit: I forgot to mention that when I run something like mvn flyway:status, I get the error message:
Flyway Error: java.lang.IllegalArgumentException: Unsupported Database: PostgreSQL
I can connect to the DB via psql, and I'm using the correct jdbc driver, so when I saw the requirements page in the documentation, I assumed that the version was explicitly checked by flyway.
What limitations do you encounter? Flyway is only tested on PostgreSQL version 9.0, that's it. It's not said that older PostgreSQL versions don't work. Just give it a try.
You could also setup a PostgreSQL 9.0 installation on your testbox to see if there is any difference.