boblail / hayfork Goto Github PK

The README points out how a second foreach block must be defined when working with associations; and that this is not adequate:

Hayfork.maintain(Haystack) do
  foreach(Book) do
    insert(:title)
    insert(author: :name)
  end
end

Instead, Hayfork could automatically define triggers based on insert(author: :name) to watch authors and repopulate the haystack.

While implementing this technique, we should decide between two paths for how Hayfork handles has_many associations. In the event that one of an article's comments is updated, we could either:

1. Wipe out all the comments entries for that post and regenerate all of them
2. Surgically replace just the entries for the updated comment

The latter is how the README's example currently works; but combining the former strategy with #1 would also remove the need for a ref_id column.

The README points out how field must be added to get this example to work:

Hayfork.maintain(Haystack) do
  foreach(Employee) do
    insert(:full_name)
    insert(:position)
    insert(:short_bio)
  end
end

Instead, Hayfork could entirely encapsulate its ability to delete the right rows from the haystack.

One option would be to add a statement_id column to the haystack and to generate a unique ID for each statement (filename and line number?). This would also be useful for debugging since it would explain why a record is present in the haystack.