Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
The SQLite extension is enabled by default as of PHP 5.0. Beginning
with PHP 5.4, the SQLite extension is available only via PECL.
Ok, I'm relatively new in PHP programming, and I was wondering what does this quoted information from official PHP site mean?
I wrote some applications that runs SQlite rather than MySQL database and I have serious concern if is it going to be deprecated from future versions of PHP.
What does it means "from now, only via PECL"?
I understand that SQlite will be available but doesn't that mean that:
PHP team will pay at least less attention on future development of PHP/SQlite integration
we could expect web hosting providers that will miss installing SQlite extension, as it is not by default any more?
Does someone have experience about what's happen when PHP "throw away" extension to PECL?
Thanks in advance.
I'm not 100% sure, but it looks to me like PHP is dropping support for the old SQLite extension in 5.4 in favour of the (newer and better) SQLite3 extension.
The SQLite3 extension is enabled by default as of PHP 5.3.0.
A major benefit of SQLite is how simple it is to setup—and having it as part of the PHP core is important to keeping it that way. I don't see that changing.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 11 months ago.
Improve this question
I need to upgrade PHP version of my project. It is PHP5.6 and I want to upgrade it to PHP8.1. I tried to search for such information but couldn't find it, thus, I want to ask. Is it better to upgrade directly from PHP5.6 to PHP8.1, or step by step (PHP5.6 -> PHP7.0, PHP7.0 -> PHP7.1, PHP7.1->PHP7.2 and etc until I reach PHP8.1)?
Upgrading step by step can help you to see what is deprecated by following the logs files and then review the code.
I have recently been made aware of this tool which ostensibly makes this process much easier. Note that I have not used it myself and as such can't speak to how well it works. It looks to be a FOSS project though which is good.
Website: https://getrector.org/
Github: https://github.com/rectorphp/rector
Updating manually as per the guides provided by vee will likely give you better understanding of the benefit each upgrade offers as well as maintaining full control over your project.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
NOTE: This is not about which better database, not at all.
Hi, my client has a shared host with the following stack:
PHP: 7.x.x
MySQL: 5.6.x
Postgres: 9.2.x
PhpMyAdmin
PhpPgAdmin
I'm able to use both MySQL(PHP) and PostgreSQL(C#, Go, Python, JS), but I personally prefer Postgres, also my client's host specs make it harder to use some SQL features like CTE which have no support in MySQL 5.6 (I know 8.0 has them).
The problem:
I plan to use Postgres, but I'm a little concerned about the combination of PHP+Postgres, since it seems that most PHP development is coupled with MySQL, for example, PhpMyAdmin is activly developed compared to PhpPgAdmin (the last release from 2018), also it seems it ALWAYS assumed that PHP runs using MySQL while Postgres is like a second citizen.
So, in your experience, should I go with Postgres or MySQL, to minimize the trouble that may arise?
Thanks.
I have used php with postgresql for about 20 years off and on. The driver is stable enough. You lack built-in support for some of the fancier data types in PostgreSQL (or used to anyway) - ranges, arrays etc.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I've got Apache + PHP 5.2.17 + mySQL on a Linux/Ubuntu server, and I was requested to upgrade the PHP version (I guess to 5.3.x or 5.4.x).
I would like to test my code in a versatile environment where I can switch among the PHP versions, and I'm trying to locate the proper software. I'm not sure whether 'UwAmp' or 'Laragon' could fit my needs (I don't mind to test it on a Windows machine).
Any suggestion is welcome. Thank you very much.
I've got Apache + PHP 5.2.17 + mySQL on a Linux/Ubuntu server, and I was requested to upgrade the PHP version (I guess to 5.3.x or 5.4.x).
Do yourself a favour and update to a version of php that have not been abandoned for years, at least 7.1. For reference, find the supported versions here. PHP 5.6 is not even in security fixes support anymore.
I would like to test my code in a versatile environment where I can switch among the PHP versions, and I'm trying to locate the proper software.
Use a local development server stack such as Ampps, MAMP, XAMP, or one of the myriad of such software. They allow for easy switching between php versions.
Alternatively, set up Travis CI with different php versions and a suite of tests. Travis is geared up to run tests suites in various PHP versions automagically.
Manually compiling and maintaining multiple versions of PHP, while doable, is not very practical if you actually wish to get things done. Using software that comes with multiple versions installed is arguably the only viable solution.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Situation:: My current web host has given me a brand new VPS today with PHP 5.2.9 (released: Feb 2009).
What I did: I asked my web host to upgrade it to latest PHP 5.3.5 so I can get all security vulnerabilities fixed.
What web host replied: No, you should not. Your PHP scripts will break. Instead you can use PHP 5.2.17.
My Question: Should I force my web host to install PHP 5.3.5 on my VPS? What problem can possibly I get by upgrading. I currently do not use any PHP 5.3 features but may use those in future. My main concern is to get fully secure from known vulnerabilities.
Please don't close this question. It's not directly related to programming but is related to PHP which only PHP experts at SO can answer, I guess.
Well, simply install PHP 5.3.5 locally and see if any of your scripts break. If everything's okay, let them install PHP 5.3.
Concerning "It will break things": PHP normally is backwards compatible. Maybe it will give you some E_STRICT errors, but those don't break scripts. But really, you should just try ;)
An old release date does not means that it has vulnerabilities. For instance most Linux distributions keep the same PHP version forever (for the lifetime of the distribution's release), but they fix vulnerabilities as they are discovered.
Just make sure that all your distribution's packages are up to date.
If its a VPS do you have root access? If so you could upgrade yourself. I imagine it should be possible with a little work to install both versions.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I'm in search of the web hosting space, and got to know the PHP version is 4.3 and MySQL Version 4.1
But i developed my application in MySQL version 5.x and PHP version 5.x
Can anyone give me the differences in versions ?
what all i cannot access now ?
Thanks...
PHP version 5 I look at as when PHP became a real language, for a whole bunch of reasons, but most importantly because it became possible to write respectable Object Oriented code.
But don't deemphasize the difference between MySQL 4 and 5 - I think it's even deeper and more significant. MySQl 5 was when MySQL became a real relational database platform, for a whole bunch of reasons, but most importantly because it became possible to write fully expressive SQL statements (starting with full subquery support).
Just those two limitations on the earlier versions are, I hope, showstoppers for you. There's no reasonable excuse for accepting less than version 5 of either.
Why not take a look at the PHP docs:
http://www.php.net/manual/en/migration5.php
http://www.php.net/manual/en/faq.migration5.php
http://www.php.net/manual/en/migration5.incompatible.php
With regards to MySQL you can track changes in versions here:
http://dev.mysql.com/doc/mysqld-version-reference/en/key-changes.html
Major new features added to MySQL 5.0 and 5.1 that may not work/won't work in 4.x can be located here:
MySQL 5.0 - http://dev.mysql.com/doc/refman/5.0/en/mysql-nutshell.html
MySQL 5.1 - http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html
Here is a basic overview of the release history. PHP 5 was a big change.
I won't go into huge detail on the differences though since PHP 4 is deprecated. Stick with PHP 5 & MySQL 5. I'd be surprised if a webhost didn't offer PHP 5 as well as 4. 4 should only be used with legacy code and should never be used for new development.