On Friday, June 14, 2019 at 12:35:19 PM UTC-7, Jake wrote: > > That isn't the exact code I'm using, I was just trying to use a simple > example with something one to one. > > For a more realistic example I have a `user account` model that has a one > to one association with another model to track the current corresponding > instance of that model. What it currently corresponds to can be updated > multiple times (not super frequently but maybe every few months). Is there > any way to force the other types of associations to update on model updates? >
Are you sure you should be using a one_to_one association? Note that 1 to 1 relationships in Sequel are represented with many_to_one on the side with the foreign key and one_to_one on the side with the primary key. It is quite strange to have a design that requires updating a primary key at runtime, which I why I get the impression you are using the wrong association type in Sequel. If you are still having problems, you should ideally post a complete self contained example showing the problem, or at the least should post your schema. Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sequel-talk. To view this discussion on the web visit https://groups.google.com/d/msgid/sequel-talk/149ec132-0d87-4503-b397-6bdd69eb353f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
