I am planning a PHP website architecture. It will be a small website with few visitors and a small data set. Data is changed exclusively by one user (administrator).
To simplify the task, I do not want to worry about a real database or XML data. I am thinking of storing all the data through PHP serialization into multiple files. For example, if there are several categories, I will store an array containing Categoryclass instances for each category.
Category
Are there any pitfalls using PHP serialization in these circumstances?
Using databases is not so difficult, and any additional time will be well studied using the database.
The traps that I see are mentioned in Yehonatan:
1. . 2. . 3. - "hackthissite.org". , - . 4. , . - , , .
, .
, , sqlite, db. , . ( ) , .
PHP -. , , :
:
. SQL-, .. ( SQL- ).
. , -. PHP , .., - . Sqlite - , , PHP.
( , Microsoft SQL Server Oracle ..).
, ( ).
, " ". , -/ . , . , , , . , select count(1) from Products, PHP , , , .
select count(1) from Products
, , , SQL-.
PHP -, , :
, , PHP ,
- ,
.
Source: https://habr.com/ru/post/1754545/More articles:python twisted thread - pythonAndroid share a comment on facebook - androidIs this the “bundle” of my web service right? Is it possible to improve? - c #jquery: open doubleclick link? - jqueryUsing getenv on Linux - c ++Скрытая переменная Vs Server, доступная на стороне клиента в javascript - javascriptInjection injection: should we all know this? - c ++Вопрос в С++ - c++how much programming programming should i know before indulging in sdl programming - cundefined variables in php - phpAll Articles