You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: user_guide_src/source/models/entities.rst
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ Assume you have a database table named ``users`` that has the following schema::
40
40
password - string
41
41
created_at - datetime
42
42
43
-
.. important:: ``attributes`` is a reserved word for internal use. If you use it as a column name, the Entity does not work correctly.
43
+
.. important:: ``attributes`` is a reserved word for internal use. Prior to v4.4.0, if you use it as a column name, the Entity does not work correctly.
44
44
45
45
Create the Entity Class
46
46
=======================
@@ -118,6 +118,14 @@ Using the raw version will bypass magic "getter" methods and casts. Both methods
118
118
to specify whether returned values should be filtered by those that have changed, and a boolean final parameter to
119
119
make the method recursive, in case of nested Entities.
120
120
121
+
Hidden properties
122
+
=================
123
+
124
+
It is possible to set properties that are only available in raw form. The property must start with an underscore. Casting cannot be applied to such fields.
125
+
This is created so that we allow our magic methods a chance to do their thing, but you can use it in another way.
0 commit comments