Comments
3 comments
-
Thanks for the suggestions Ulrich, we'll keep them in mind for a future release. I think the cross-database support will appear very soon based on the number of requests we're getting for it.
Thanks,
Bart -
I agree with Ulrich. This was an option in Version 2 and to me is a much desired freature. The list in the joins suggestions would work much better too. I have a standared that all table contain a created and modified date columns, and I'm being presented with the following:
.[Created_By] = [c].[Created_By]
.[Created_Dt] = [c].[Created_Dt]
.[Modified_By] = [c].[Modified_By]
.[Modified_Dt] = [c].[Modified_Dt]
.[Ticket_Id] = [c].[Ticket_Id]
Where Ticket_Id is the only PK/FK relationship. I know I can turn off matching column names but if the PK was first, this would not be necesary.
Dave -
Hi there,
Thanks for posting.We might well add an option for grouping of JOIN conditions by their type in a future release.
Cheers,
Bart
Add comment
Please sign in to leave a comment.
I'd like to have an option to switch off the alpha sort for the columns in the column picker window.
For me, it works much better to find a column in the order in which they are defined in the table.
Cross-database support would be very much appreciated as well
Thanks
Ulrich