Setting
class Setting extends BaseModel
Base setting model. To keep the table length from growing arbitrarily long settings are store as base64 encoded json objects.
Items with a protected value of '1' are not editable and must be managed directly in the database. As such, you should probably use that flag sparingly. Srsly.
Properties
| int | $id | ID | |
| string | $uuid | UUID | |
| string | $label | Label | |
| string | $value | Value | |
| datetime | $created_at | Created time | |
| datetime | $modified_at | Modified time | |
| boolean | $protected | Protected value |
Methods
Phalcon has this bug where if you enumerate a relation then try to set it via the magic setter, it won't save.
Initialize method for model.
No description
Returns table name mapped in the model.
Details
in BaseModel at line line 13
getResultsetClass()
in BaseModel at line line 25
boolean
hasProperty(string $str)
Determine if the model has a public property.
Useful in determining valid sorting options on the front end.
in BaseModel at line line 40
BaseModel
setRelated(string $relation, mixed $value = array())
Phalcon has this bug where if you enumerate a relation then try to set it via the magic setter, it won't save.
I think it has something to do with implicit transactions, but I'm not entirely sure...
at line line 64
initialize()
Initialize method for model.
at line line 96
beforeUpdate()
at line line 112
string
getSource()
Returns table name mapped in the model.
at line line 123
static User[]
find(mixed $parameters = null)
Allows to query a set of records that match the specified conditions
at line line 134
static User
findFirst(mixed $parameters = null)
Allows to query the first record that match the specified conditions