* Indicates if the model should be timestamped. If you do not wish to have these columns managed automatically, set the $timestamps property on your model to false: class Post extends Model * The primary key for the model is not an integer.īy default, a model will expect created_at and updated_at columns to exist on your tables. If you wish to use a non-incrementing or a non-numeric primary key you must set the public $incrementing property to false. Models will assume that the primary key is an incrementing integer value, which means that by default the primary key will be cast to an integer automatically. You may define a $primaryKey property to override this convention. Models will assume that each table has a primary key column named id. String that contains the connection name that's utilised by the model by default.
Values are fields made hidden when serializing the model data. Values are fields made visible when serializing the model data. Values are fields guarded from mass assignment. Values are fields accessible to mass assignment. Values are encoded as JSON before saving and converted to arrays after fetching. Values are converted to an instance of Carbon/DateTime objects after fetching.īoolean that if true will automatically set created_at and updated_at fields.
Primary key name used to identify the model.īoolean that if false indicates that the primary key is not an incrementing integer value.īoolean that if true indicates that the model exists. There are some standard properties that can be found on models, in addition to those provided by model traits. The table name is a snake case name of the author, plugin and pluralized record type name. The $table protected field specifies the database table corresponding the model. The most basic representation of a model used inside a Plugin looks like this: namespace Acme\Blog\Models All model classes must extend the Model class. In most cases, you should create one model class for each database table. The model configuration directory name matches the model class name written in lowercase. The model configuration directory could contain the model's list column and form field definitions. ┃ ┃ ┣ 📜 columns.yaml <= Model config files An example of a model directory structure: 📂 plugins
Model classes reside in the models subdirectory of a plugin directory. Models allow you to query for data in your tables, as well as insert new records into the table. Each database table has a corresponding "Model" which is used to interact with that table. Winter provides a beautiful and simple Active Record implementation for working with your database, based on Eloquent by Laravel.
0 kommentar(er)
