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
(This is an attempt to pair down what is a more complex model on my end; hope it conveys the bug.)
Tracing through:
# A resource is considered to be new if the repository# does not have statements where subject == resource typedefnew_record?
!self.class.repository.has_subject?(subject)end
That blank node acts as a variable, so it matches so long as there is anything in the backing store. In other words, #new_record? produces true so long as any triple exists in the backing store.
This issue occurs when connected to Fuseki:
(This is an attempt to pair down what is a more complex model on my end; hope it conveys the bug.)
Tracing through:
That blank node acts as a variable, so it matches so long as there is anything in the backing store. In other words,
#new_record?
producestrue
so long as any triple exists in the backing store.Elsewhere:
Might be time to resolve that TODO.
This shows in Rails like so:
#form_for
eventually calls@article.id
, which then crashes.The text was updated successfully, but these errors were encountered: