I've hacked up a cron job to take advantage of the newer yaml_db gem
(http://github.com/ludicast/yaml_db) using Adam's gist (http://
gist.github.com/231874). It all works swimmingly except for some
reason, the yaml_db file likes to cut off the last bunch of records.
It's really strange, and I cannot seem to figure out what the problem
is. It's like it gets sick of creating yaml or something and just
stops, but without any kind of failure message. It seems to work fine
locally, but on heroku, this problem creeps up, albeit with different
data.
At the end of the db file I see this. Notice the last record is
incomplete, but it also skipped the remaining records:
---
status_logs:
columns:
- id
- listing_id
- status
- status_date
- price
- created_at
- updated_at
records:
- - "1"
- "1"
- available
- "2010-02-14"
- "1395"
- 2010-02-14 20:48:35.479099
- 2010-02-14 20:48:35.479099
- - "2"
- "2"
- available
- "2010-02-14"
- "950"
- 2010-02-14 20:48:46.132901
- 2010-02-14 20:48:46.132901
- - "3"
- "3"
- available
- "2010-02-14"
-
--
You received this message because you are subscribed to the Google Groups
"Heroku" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en.
