On Feb 10, 2010, at 4:31 PM, Pito S. wrote:
Marnen Laibow-Koser wrote:
To the OP: if this column is just going to be the id with a constant
prefix, then you don’t need it in the DB!
It’s initializing existing records in a migration. Over time the match
will not be present.
To the other point about “||” meaning concatenation. Thats what got me
thinking as some other SQLs use “+” and others use CONCAT().
|| is standard. That said, MySQL doesn’t follow the standard and
treats || as OR. Unless you start it up in ‘ansi’ mode.
Might not matter a bit for you, but if it does, you could always do
the concatenation in rails via find/save/update_attribute. Slower,
but would work.
Here’s something else that just got me as I don’t use Sqlite much…
named_scope :approved, :conditions => “is_approved = true”
Will fail on sqlite as it doesn’t recognize true.
named_scope :approved, :conditions => [“is_approved = ?”, true]
works though. I do the  thing for everything else but figured
‘true’ was safe. Guess not.