Please start to use join syntax instead of an IN clause:
select a.first_name,
a.actor_id,
fc.film_id,
c.name,
c.category_id
from actor a
left join film_actor fa
on a.actor_id = fa.actor_id
left join film_category fc
fa.film_id = fc.film_id
left join category c
on fc.category_id = ...
I used to use that one for manually formatting code to publish on sqlblog.com, because that site uses the antithesis of blogging tools, Community Server.
On sqlperformance.com it's WordPress so I have a highly customized version of WP-GeSHi highlighting - I just drop code in and it makes it all pretty colors for me.
Formatting is less of an issue for me since I am pretty anal about formatting right from the start.
I have a stored procedure which inserts two records into a table, the difference between the records is that the time column of the second record is @MinToAdd after the first:
CREATE PROCEDURE CreateEntry
/*Other columns*/
@StartTime time(2),
@EndTime time(2),
@MinutesToAdd small...
dysfunctional family - male gay couple with a daughter, old man (Ted Bundy) married to young hottie (Sofia Vargara) with a son, wacky couple with a son and two daughters. I spit out portions of beverage at least once during every episode.
@swasheck The edit chain ostensibly makes the question more objective, while altering the character of the original post, and taking out relevant information like his closeness with the employee and the fact that he has a child. The idea that those things can be separated is ludicrous. It is StackExchange's fatal weak spot, the anal-retentive quest to always be more and more Q&A and less and less Forum.
i.e. no recipes on the cooking stackexchange. People WANT a one-stop community. If the Q&A portion isn't where it needs to be, people WILL NOT come to a Q&A site where they have to pick and choose which questions to ask where. They'll just go back to the most popular and friendly sociable forum.
@swasheck Something in one of the comments triggered me to go back and see why what they were talking about was missing.
Please start to use join syntax instead of an IN clause:
select a.first_name,
a.actor_id,
fc.film_id,
c.name,
c.category_id
from actor a
left join film_actor fa
on a.actor_id = fa.actor_id
left join film_category fc
fa.film_id = fc.film_id
left join category c
on fc.category_id = ...
I have a stored procedure which inserts two records into a table, the difference between the records is that the time column of the second record is @MinToAdd after the first:
CREATE PROCEDURE CreateEntry
/*Other columns*/
@StartTime time(2),
@EndTime time(2),
@MinutesToAdd small...
