4 ms·
This is great, thank you. I was literally going to start working on a Rails A/B framework after reading HN today. Funny how that works. Edit: In the newest v
by defen 17y ago
This is great, thank you. I was literally going to start working on a Rails A/B framework after reading HN today. Funny how that works.
Edit: In the newest version of Rails (2.3.3) and IIRC a few versions before that as well, the timestamp field is called created_at, not created_on - I was getting an error when running the migration.
- patio11 17y agoThanks for the bug report. I can't address it right now as I'm at an Internet cafe, with my laptop spending the night at my designer's house, but I'll fix it in the morning. Off the top of my head I don't remember anything that actually uses the timestamps, so feel free just to comment out the line (was it assigning an index, maybe?) that caused the exception.
- charliepark 17y agoYou're right; it was assigning an index, on line 11 of the migration. Changing it to "created_at" works fine.
- patio11 17y agoAnd fixed. Thanks for the report.