[Solved] updating base64_encode() serialized array on MYSQL Databases? [closed]

Question

That is why storing base64 encoded serialized data in the database is extremely bad idea.

You have to redesign your database, getting rid of base64_encode and serialized data.
While using base64 with database makes absolutely no sense by any means, storing serialized data in the database is like mending an electronic device with stone hammer.

The main difference between database and ancient scroll of parchment is to give an individual access to whatever bit of information, and you are ruined that purpose completely, using stone-age way of storing data. Please, educate yourself and learn proper ways of using databases.

Database itself IS a perfect storage for the data structure from your example. You just have to add another table with fields date, amount, deposit and record_id and link that table to one that currently contains that base64 encoded array.

Accepted Answer

That is why storing base64 encoded serialized data in the database is extremely bad idea.

You have to redesign your database, getting rid of base64_encode and serialized data.
While using base64 with database makes absolutely no sense by any means, storing serialized data in the database is like mending an electronic device with stone hammer.

The main difference between database and ancient scroll of parchment is to give an individual access to whatever bit of information, and you are ruined that purpose completely, using stone-age way of storing data. Please, educate yourself and learn proper ways of using databases.

Database itself IS a perfect storage for the data structure from your example. You just have to add another table with fields date, amount, deposit and record_id and link that table to one that currently contains that base64 encoded array.