You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just like db.NewSelect().Model(entity), after specifying the Model, you can read the table name and alias information automatically. However, it is a bit difficult for Join because we need to hardcode the table name and alias ourselves. This work is obviously redundant and unnecessary. I think we can completely solve this problem by using the concept of JoinModel (similar to Model), which can improve efficiency and reduce code duplication.
At the same time, for Join, although we need to write INNER JOIN or LEFT/RIGHT JOIN ourselves, I also think this can be solved by adding a few methods:
LeftJoin()
RightJoin()
I have an idea to submit a Pull Request, but before that, I would like to discuss their feasibility first.
The text was updated successfully, but these errors were encountered:
Just like
db.NewSelect().Model(entity)
, after specifying the Model, you can read the table name and alias information automatically. However, it is a bit difficult for Join because we need to hardcode the table name and alias ourselves. This work is obviously redundant and unnecessary. I think we can completely solve this problem by using the concept of JoinModel (similar to Model), which can improve efficiency and reduce code duplication.At the same time, for Join, although we need to write
INNER JOIN
orLEFT/RIGHT JOIN
ourselves, I also think this can be solved by adding a few methods:I have an idea to submit a Pull Request, but before that, I would like to discuss their feasibility first.
The text was updated successfully, but these errors were encountered: