+1 i cannot agree with you more! 'join' sql should be used carefully, we have received more and more feedback about page refresh time in the case of large amount of data.
wu shaoj <[email protected]> 于2021年3月11日周四 上午9:52写道： > We can do it after SPLITING BIG JSON. > > > From: CalvinKirs <[email protected]> > Date: Thursday, March 11, 2021 at 09:44 > To: [email protected] <[email protected]> > Subject: Re: [DISCUSS] sql improvement > We can split some SQL, maybe we can try to do it first. At least change > what can be changed first. > > > Best wishes！ > CalvinKirs > > > On 03/11/2021 00:02，lidong dai<[email protected]> wrote： > usually it is very difficult to implement all the features as you said. > > one more better idea is that we can impove the performance the join sql if > this sql query is indeed very slow > > > > Best Regards > --------------- > DolphinScheduler(Incubator) PPMC > Lidong Dai > [email protected] > --------------- > > > On Mon, Mar 8, 2021 at 12:03 PM CalvinKirs <[email protected]> wrote: > > The database belongs to the underlying service, and most of the > bottlenecks are often in the database. It is recommended that the database > is only used as a tool for the data store, and not concerned with the > business. Therefore, I suggest that it is better not to write all kinds of > join SQL, it may be better to leave it to the business layer to do the > association. What do you think? > > > Best wishes！ > CalvinKirs > > -- DolphinScheduler(Incubator) PPMC BaoLiang 鲍亮 [email protected]
