Notes and bugs generated during the use of h:i:s and y-m-d

When the selected dates are 2022-02-09 Make screening conditions when , There's no data , The parameters passed to the backend here are “2022-02-09 00:00:00”,“2022-02-09 00:00:00”, In this way, the screening range is very narrow . Because the back-end code is accurate to seconds

Here are some Wrong writing .

 The back-end code is accurate to seconds 

//  The back-end code is accurate to seconds --- Wrong writing 
            <if test="applyStartTime != null and applyEndTime != null">
                <![CDATA[
                and DATE_FORMAT(t.apply_time
                            , '%Y-%m-%d %H:%i:%s') >= DATE_FORMAT(#{
    applyStartTime}
                            , '%Y-%m-%d %H:%i:%s')
                and DATE_FORMAT(t.apply_time
                            , '%Y-%m-%d %H:%i:%s') <= DATE_FORMAT(#{
    applyEndTime}
                            , '%Y-%m-%d %H:%i:%s')
                ]]>
            </if>

Here are some Correct code slice .

 It can only be accurate to the number of days 

       <if test="applyStartTime != null and applyEndTime != null">
                <![CDATA[
                and DATE_FORMAT(t.apply_time
                            , '%Y-%m-%d') >= DATE_FORMAT(#{
    applyStartTime}
                            , '%Y-%m-%d')
                and DATE_FORMAT(t.apply_time
                            , '%Y-%m-%d') <= DATE_FORMAT(#{
    applyEndTime}
                            , '%Y-%m-%d')
                ]]>
            </if>