You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm confused by the "Created and Updated At Columns" section of the readme. It states "Although you can use created_at and updated_at methods, you may still want the columns in SimpleDB to be created_at and updated_at.", which to me says that we could go ahead and set the columns to created_at and updated_at. But the example following this statement sets them to "created" and "updated", not "created_at" or "updated_at". The first part of the subsequent "note" seems to recommend setting the columns to "created_at" and "updated_at", but the example given in the note again uses "created" and "updated".
Is it okay to use created_at and updated_at so that we can use these in our queries just as we do in regular active_record queries?
The text was updated successfully, but these errors were encountered:
I'm confused by the "Created and Updated At Columns" section of the readme. It states "Although you can use created_at and updated_at methods, you may still want the columns in SimpleDB to be created_at and updated_at.", which to me says that we could go ahead and set the columns to created_at and updated_at. But the example following this statement sets them to "created" and "updated", not "created_at" or "updated_at". The first part of the subsequent "note" seems to recommend setting the columns to "created_at" and "updated_at", but the example given in the note again uses "created" and "updated".
Is it okay to use created_at and updated_at so that we can use these in our queries just as we do in regular active_record queries?
The text was updated successfully, but these errors were encountered: