Open kolinfluence opened 1 week ago
JOIN is ok, foreign key should be avoided, do you have real requirements?
@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
as titled