try custom queries direct to the DB, perhaps it's something to do with SilverStripe enabling ANSI
Does anyone here have a strong preference for which pattern to use when creating a
- $obj = MyDataObject::create([
- 'Field' => 'Value',
- $obj = MyDataObject::create();
- $obj->Field = 'Value';
vs something else?
I notice if the later is well annotated, code-intel gives those properties quicker references, and make them traversable, but there's repeated use of the
the first is setting the initial state - e.g. when the object is created from the DB. If you then perform a write, nothing will happen (unless there is no ID).
The second explicitly updates an existing (in memory) DataObject, which flicks the
changed status. Writes will see there are changes to record, and so continues happily.
the better equivalent for what you're trying to achieve with the first call is
MyDataObject::create()->update(['Field' => 'Value'])
of course, this is a little nitpicky, because if you're creating a brand new object, then there's no ID which means
isInDatabase is false, meaning a write happens and folks are generally none the wiser.
But this is certainly a gotcha I've run into before (a long time ago, but it's a lasting memory, which still holds true).
In terms of strong preference over
->Field = ..., no I don't think there is one.