PHP

serialize() php

<?php

$arrayName = array();
array_push($arrayName, "messie");
array_push($arrayName, "cr7");
print_r($arrayName); //output is => Array ( [0] => messie [1] => cr7 )
$serial = serialize($arrayName);
print("<br>");
print($serial); //output is =>a:2:{i:0;s:6:"messie";i:1;s:3:"cr7";}

// a is arrray ; 2 is the number of the ietems insid the array ;
 //i is the index ; s is the number of the chracters ;
$serial=unserialize($serial);
print("<br>");
print_r($serial);//output is => Array ( [0] => messie [1] => cr7 )



?>

php serialize array

$array["a"] = "Foo";
$array["b"] = "Bar";
$array["c"] = "Baz";
$array["d"] = "Wom";

$str = serialize($array);

php serialize()

php array to be storable value in $_SESSION:
 serialize($array)
  serialized array element to be output on page:
unserialize($serializedArray)

php array serialize

//If you plan to serialize and store it in file or database use below syntax
//to safely serialize
$safe_string_to_store = base64_encode(serialize($multidimensional_array));

//to unserialize...
$array_restored_from_db = unserialize(base64_decode($encoded_serialized_string));

serialize php

Please! please! please! DO NOT serialize data and place it into your database. Serialize can be used that way, but that's missing the point of a relational database and the datatypes inherent in your database engine. Doing this makes data in your database non-portable, difficult to read, and can complicate queries. If you want your application to be portable to other languages, like let's say you find that you want to use Java for some portion of your app that it makes sense to use Java in, serialization will become a pain in the buttocks. You should always be able to query and modify data in the database without using a third party intermediary tool to manipulate data to be inserted.

I've encountered this too many times in my career, it makes for difficult to maintain code, code with portability issues, and data that is it more difficult to migrate to other RDMS systems, new schema, etc. It also has the added disadvantage of making it messy to search your database based on one of the fields that you've serialized.

That's not to say serialize() is useless. It's not... A good place to use it may be a cache file that contains the result of a data intensive operation, for instance. There are tons of others... Just don't abuse serialize because the next guy who comes along will have a maintenance or migration nightmare.