We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
as titled
The text was updated successfully, but these errors were encountered:
JOIN is ok, foreign key should be avoided, do you have real requirements?
Sorry, something went wrong.
@jcwangxp if foreign key doesnt add much overhead, can support but otherwise can do another version that supports it.
definitely have use case for implementation value.
but i prefer if u can keep this as lightweight as possible. in fact i think u can do an x version that extremely lightweight
3 versions x <- ultra lightweight normal <- simple version without foreign key / join e version with foreign key / join
No branches or pull requests
as titled
The text was updated successfully, but these errors were encountered: