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.
Related
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 1 year ago.
Improve this question
How time consuming is migrating a medium/large sized legacy Symfony application from version 2.3 to 4.4 compared to rewriting it in a different framework?
From the research I've done it seems like quite a lot of stuff has changed between these versions so I'm trying to weigh this decision up against just rewriting the whole thing in Laravel (the framework I'm experienced in). I'm trying not to get stuck in a wormhole of rewriting abandoned code.
The main reason for the upgrade is security fixes, running Symfony 2.3 in 2021 doesn't seem like the best idea to me. The codebase won't need any changes in the near future.
Following is an overview of used packages.
Upgading you symfony version that much means 3 steps:
upgrading your php version (PHP 5.3.3 to 7.1.3)
upgrading your package (most of them will not work any more or have lot of changes)
upgrading symfony
It mostly depends of your code coverage: if you have a good code coverage, you will be able to quickly identify remainings bug
otherwise it depends on your legacy:
are best practice used?
is the code clear?
is the code well decomposed?
For larger project, i don't recommand to create a new one: it cost a lot of money and may prouce bugs and regression
The best way to do it is step by step. Determine which package to upgrade one by one, do it and push it in production with the apropriate code coverage.
Start with your php version: on local, have your devellopement be run in higher php version to identify most bugs and correct them
Manage each of your abandonned project to replace them with the recommended one
we had to deal with phpexcel to php spreadsheet. We identify each place where it was used in the application, and update each of them, one by one (having both package on project). When phpexcel wasn't used anymore, we deleted it
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 7 years ago.
Improve this question
I'm looking at update codebase I'm working with from PHP5 to PHP7 when PHP7 reaches full release (largely due to the fact the speed gains and the ?? operator could really help our site).
As there are deprecated functions, and some things that are altered between the versions, I'm considering using filemtime on php files before including them to see if I should include functions that will modify php7's behavior to act a bit more like php5 in regards to those files. Although this will work on the existing server, I know various copy methods (some down the pipeline that it will be hard to control) will likely change the modified date as files are copied.
Is there a method for determining which php version a file is written with or compatible with and interpreting them appropriately, or is this hacky and risky solution really my best bet?
On solution I see was inspired while hunting for solutions here: link
In short...
create two different localhost servers
set each localhost to link to a different version of php
write code afterwards that pulls from the old code as if it were pulling from a different server.
steadily migrate files from old to new version of php after initial migration.
As a result, instead of having to migrate the entire codebase, it can be migrated a chunk at a time, without having to do all-or-nothing all-at-once. It also should be more durable than the filemtime solution. The downside is that it makes it harder to immediately integrate old code into new code.
Still interested in better solutions, but at least it's a solution.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
My web host is running a different PHP then the one Laravel is using. To overcome this I want Laravel to use another version of PHP. I'm having trouble finding where to do this. My question is it possible and if so where can I change it.
Laravel has a version of php as a dependancy. You cannot use a version of Laravel that requires, for example, PHP>=5.4 on a server that is using a version of PHP below 5.4.
If you have to use an older version of PHP, you need to use an older version of Laravel that supports your desired version of PHP.
Try searching the Laravel website for older versions, or consider upgrading your version of PHP to match Laravel's requirements.
If your web host is not running a version of PHP that supports Laravel (5.4+), they are a dangerous and unprofessional webhost and you should find a new one. PHP 5.3 and lower have been end-of-lifed (http://php.net/eol.php), meaning they may (and likely do) contain unpatched security holes and other bugs that will never be fixed.
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.