This is from a discussion between myself, @denibertovic, and @bitemyapp. Because of the way QQ scopes things, schema.txt in this repo is not in the same scope when the user includes the decls into their own app. The result is that persistent can't figure out that SnapAuthUserId is a primary key and thus if you reference it in another table, it will not create a foreign key. The solution is to manually tell persistent's TH that the column is a reference.
This is from a discussion between myself, @denibertovic, and @bitemyapp. Because of the way QQ scopes things,
schema.txtin this repo is not in the same scope when the user includes the decls into their own app. The result is that persistent can't figure out thatSnapAuthUserIdis a primary key and thus if you reference it in another table, it will not create a foreign key. The solution is to manually tell persistent's TH that the column is a reference.