Ok,
It turns out that the two tables have a circular relationship using
different fields, so that wasl ikely the cause of this bug.
I fixed it by changing the relationship to be deferrable.
So the bug is invalid.
On 18/06/2019 12:21, Bugs in DBIx-Class-Fixtures via RT wrote:
Show quoted text> Greetings,
>
> This message has been automatically generated in response to the
> creation of a trouble ticket regarding:
> "_get_sorted_sources is wrong about relationship between two tables",
> a summary of which appears below.
>
> There is no need to reply to this message right now. Your ticket has been
> assigned an ID of [rt.cpan.org #129844]. Your ticket is accessible
> on the web at:
>
>
https://rt.cpan.org/Ticket/Display.html?id=129844
>
> Please include the string:
>
> [rt.cpan.org #129844]
>
> in the subject line of all future correspondence about this issue. To do so,
> you may reply to this message.
>
> Thank you,
> bug-DBIx-Class-Fixtures@rt.cpan.org
>
> -------------------------------------------------------------------------
>
> A have a table class C with an accessor:
>
> "uid",
> { data_type => "integer", is_nullable => 1 },
>
> and another class U with an accessor that is a foreign key to C
>
> "uid",
> {
> data_type => "integer",
> is_foreign_key => 1,
> is_nullable => 1,
> },
>
> Both of these columns are unique, and both have belongs_to relationships.
>
> But DBIC::Fixtures insists on adding records for the U table before the
> C table.
