On Aug 8, 2011, at 4:35 AM, Nick Shore wrote:
I was in fact using existing databases - actually the update I'm working on
has a migration involved in it too. I didn't mention it originally as I'd
ruled it out as the cause, but that actually helped fix the problem. Since I
was already
Nick,
I was in fact using existing databases - actually the update I'm working on has
a migration involved in it too. I didn't mention it originally as I'd ruled it
out as the cause, but that actually helped fix the problem. Since I was already
migrating the data (with custom entity migration
On Aug 4, 2011, at 2:30 PM, Nick Zitzmann wrote:
I tried searching around and found one other person who had the same
problem[1], but no one followed up with a good solution for existing
databases.
I have an entity with a many-to-many relationship to itself, called parents
and children.
I tried searching around and found one other person who had the same
problem[1], but no one followed up with a good solution for existing databases.
I have an entity with a many-to-many relationship to itself, called parents
and children. And when I take a database that was made by an
