Signed-off-by: Stan Bondi <stan@stanley-pc.(none)>

Signed-off-by: Dejan Geci <dejan.geci@gmail.com>

Signed-off-by: Daniel Bøndergaard <db@helmstmt.com>

This is in reference to issue #1261, where Model->get_key() returns
the key from the $attributes instead of from the $original property.
This breaks the functionality of a model with a primary key that may
change, as the SQL generated will be something like:

UPDATE `model` SET `key` = 'new-key' WHERE `key` = 'new-key';

Which won't update the model in the database.

When you had a synched Eloquent model (e.g. without changed values) but
one of those values is `null`, then that value would be considered as
dirty. `Eloquent::changed` returns false, but the value is present in
`Eloquent::get_dirty`.

This fix makes sure that a `null` value in `$attributes` is only
present in `get_dirty` when it wasn't at all *set* in `$original`.

Signed-off-by: Callum McIntyre <mcintyre1994@gmail.com>

Changed timestamp function in database/eloquent/model.php from protected to public. Allows eloquent model timestamps to be updated without actually changing any data.
git push fork minor/unprotect-eloquent-timestamps
git status
git

#

Signed-off-by: Callum McIntyre <mcintyre1994@gmail.com>

switched from default "tinyint" which creates a tinyint(4) to the
standard mysql boolean type "tinyint(1)"

reference to #991

Signed-off-by: Josh Miller <josh@joshmmiller.com>

Signed-off-by: Rack Lin <racklin@gmail.com>

Calling update() on an eloquent model has no way of overriding
the timestamp that should be set if $timestamps is set on the
model. This changes that so it uses the timestamp() function
which is an easy way to over ride the type of timestamps used.

Signed-off-by: Jason Lewis <jason.lewis1991@gmail.com>

Fix a bug with Eloquent model classes and isset() when eager loading a relationship returns an empty result set.