Just went through the same decision myself last week.
DBVarchar all the way...
Hello all... given that I don't fully get how SS implements query optimisation techniques, I just wondered what the most efficient way of getting just a single DB column for some records would be: build it using an
SQLSelect, or use
@Marley has joined the channel
@heggsta Always default to using the ORM first. If you have a look at
DataObject::get_one() (and others) you'll see how they leverage an internal query-cache.
Goes without saying, but try not to optimise until you need to optimise.
thanks @theruss - i'll dig a bit deeper at how they work
There are definetly cases when
SQLSect and friends should be used, but in my experience, they are few.
i actually ended up using an
SQLSelect because it was easy enough, but if other methods optimize with internal caching that sounds like the best way to do things