Geek asks and answers

Is it possible to be intentionally strict with the table structure in RedBeanPHP?

I really like the RedBeanPHP concept. During the development process, you do not need to worry about using the database, RedBean does everything for you. Tables shape themselves while you work, and when you are happy with tables, you freeze them. The only problem I see is moving the project to a new system. One of the great parts of ORM is that the database table is created from the PHP model, which means that you do not need to constantly export the database structure to make it safe. I don’t see how this could be done using RedBean, since it forms the table structure after repeated use over time with variable data.

I understand that defining the table structure in advance would weaken the meaning of using RedBean in the first place, but I would at least like to determine the database structure in PHP after using RedBean in "dynamic mode" during the time so that moving the project between systems does not it would be just as painful.

I hope that I have clearly stated my reasons for someone to contact RedBeanPHP and possibly have come across this issue earlier.

thank

+3
source share
3 answers

, - script, FUSE bean , bean bean ( bean) . , script .

, - , .

0

, RedBean:

$bean->setMeta('cast.myproperty', 'text');

: http://redbeanphp.com/extra/meta_data

+2

One could extend the method R::freezeto create an empty sqlite database and use R::syncSchemait to fill it with structure. Then in production, the task can use the same method to cancel the process.

+1
source

More articles:


All Articles