How can we help you today? How can we help you today?

Order By Fields Start On A New Line - Regardless

I have found that even though I have not selected 'On a new line' option in the Column Placement options, the fields are consistently started on a new line in the Order By clause of my queries. The placement is correct through the rest of the query.

Example: 
SELECT   mp.Marketing_Project_Name
        ,Count(oy.Opportunity_Id)
FROM     dbo.Opportunity oy with (NOLOCK) 
INNER JOIN dbo.Telemarketing_Prospect tp with (NOLOCK) 
        ON oy.Telemarketing_Prospect_ID = tp.Telemarketing_Prospect_Id
INNER JOIN dbo.Marketing_Project mp with (NOLOCK)
        ON tp.Marketing_Campaign_Project_ID = mp.Marketing_Project_Id
WHERE   mp.Status <> 'Completed'
        AND oy.Delivery_Date IS NOT NULL
        AND LEFT(oy.Pipeline_Stage, 1) = 5
GROUP BY mp.Marketing_Project_Name
ORDER BY
         mp.Marketing_Project_Name

This is more of a nuisance than a serious problem and seems to be something that could be easily corrected.

One other thing, is there a chance that you could include the option to align the first line of the Join condition, the On statement, with the begining of the Join statement with each susequent condition indented. This is a convention that I have used for many years.

Example: 
Select a.*
From a
Inner Join b
on a.a = b.a
       and a.b = b.b

Other than that and the few other minor glitches already mentioned this is a great product that has already saved me substantial time and effort.
RogueDog
0

Comments

1 comment

Sort by
  • Andras B
    RogueDog wrote:
    I have found that even though I have not selected 'On a new line' option in the Column Placement options, the fields are consistently started on a new line in the Order By clause of my queries. The placement is correct through the rest of the query.

    Example: 
    SELECT   mp.Marketing_Project_Name
        ,Count(oy.Opportunity_Id)
FROM     dbo.Opportunity oy with (NOLOCK) 
INNER JOIN dbo.Telemarketing_Prospect tp with (NOLOCK) 
        ON oy.Telemarketing_Prospect_ID = tp.Telemarketing_Prospect_Id
INNER JOIN dbo.Marketing_Project mp with (NOLOCK)
        ON tp.Marketing_Campaign_Project_ID = mp.Marketing_Project_Id
WHERE   mp.Status <> 'Completed'
        AND oy.Delivery_Date IS NOT NULL
        AND LEFT(oy.Pipeline_Stage, 1) = 5
GROUP BY mp.Marketing_Project_Name
ORDER BY
         mp.Marketing_Project_Name

    This is more of a nuisance than a serious problem and seems to be something that could be easily corrected.

    One other thing, is there a chance that you could include the option to align the first line of the Join condition, the On statement, with the begining of the Join statement with each susequent condition indented. This is a convention that I have used for many years.

    Example: 
    Select a.*
From a
Inner Join b
on a.a = b.a
       and a.b = b.b

    Other than that and the few other minor glitches already mentioned this is a great product that has already saved me substantial time and effort.

    Hi,

    the first issue concerning ORDER BY we have fixed, so it should work properly in the final release.

    Concerning the extra option I will save it for future releases (we have frozen features and code for the current release)

    Many thanks for your feedback,

    Andras
    Andras B
    0

Add comment

Please sign in to leave a comment.