Home » Php » Does static variables in php persist across the requests?

Does static variables in php persist across the requests?

Posted by: admin April 23, 2020 Leave a comment

Questions:

Static variable gotcha in php

I am from Java background and have switched to php for one project recently.
I have found one unexpected behaviour in php.

Value set to some static variable is
not staying persistent across the
requests.

I am not sure if this is the expected bahaviour. Because in java , you can always persist very commonly used variables or say constants like dbname,hostname,username,password across the requests so that you don’t have to read them always from local property files.

Is this behaviour normal ? And if it is normal then is there any alternative by which I can persist values assigned to variables across the requests ?

Can someone suggest me a better way of doing this in php?

How to&Answers:

No, while a static variable will stay for the current request you’ll need to add it to a session to persist it’s value across requests.

Example:

session_start();

class Car {
    public static $make;
    public function __construct($make) {
        self::$make = $make;
    }
}

$c = new Car('Bugatti');
echo '<p>' . Car::$make . '</p>';
unset($c);

if (!isset($_SESSION['make'])) {
    echo '<p>' . Car::$make . '</p>';
    $c = new Car('Ferrari');
    echo '<p>' . Car::$make . '</p>';
}

$_SESSION['make'] = Car::$make;

echo '<p>' . $_SESSION['make'] . '</p>';

Answer:

Static variables are only applicable to one single request. If you want data to persist between requests for a specific user only use session variables.

A good starter tut for them is located here:
http://www.tizag.com/phpT/phpsessions.php

Answer:

If you begin working with complex data sets across sessions you may want to look into storing data in objects that get serialized to the database and drawn out on session restore.

Variables in PHP aren’t meant to be persistent. The flow of your application (the stack) is executed start to finish on each page run. There is nothing living in the background that continues your logic or application. The closest thing is a session but you do not want to store information like db access etc. in there.

Your database configurations should be in some sort of config or environment file that are accessed one time to connect to the database, once a connection has been made you can simply query whenever needed and use the connection handle to identify what connection to use.