Donno like Jon boy. Video game nerds in general have shit music tastes but there's some good ones in the tf.tv Last.fm group.

So more people will step up and the game goes on.

TF2 confirmed dead 4+ years and counting

Cheers Slin

Twitch: http://www.twitch.tv/russianguyovich
Steam: http://steamcommunity.com/id/russianguyovich/
ETF2L: http://etf2l.org/forum/user/43331/

Finally got some decent internet and sorted out my stream today! Got a couple VODs on there if you want to check the quality (ignore the testing ones). Scotland flag please :)

I've been playing competitive TF2 for about 3 and a half years and I'll mostly be streaming pubs, lobbies, 6v6 and Highlander as I'm too bad for MGE. I may also do the odd cast here and there too!

Can't wait for the Twitch chat

Oh and the games too I guess

VOD is here patty melt bros

https://www.youtube.com/watch?v=o5CNX9tC8Wk

I switched to Avast! from AVG a few years ago and not had any problems. You have to re-register every year for the free version but it takes about 30 seconds through the application. Just remember to add your steam folders to the exclusion list and enable silent mode - very unobtrusive.

Thank fuck ETF2L isn't like this.

The idea behind identity columns is the value is auto generated by the database engine as opposed to a naturally-defined key on one or multiple columns. While you usually don't specify the value of this identity column during an insert statement, there are ways to perform a manual insert assuming it's a unique value (treated as a constraint).

One big advantage with using identities for a surrogate key compared to natural keys (such as map name) is that your referential integrity will be intact compared to a scenario where the information used for your natural keys might have to be updated.

Even if you don't intend on using an identity column for referential integrity, they are good for large tables which would benefit from a clustered index being present to optimise query plans that would otherwise take too large a storage hit if creating a nonclustered index on one or several columns on that table.

Just to mention, I come from primarily a SQL Server background. The Oracle equivalent to identity columns are sequences.

+1

Can't say I've ever created a UML diagram before I started developing which didn't end up binned because of some changes to the design made along the way. Just make sure you don't store duplicate, or even worse, conflicting information where it isn't needed. Consider using identity columns where a primary key isn't easily defined (i.e. unique constraint isn't possible) and use them as foreign keys in your dependant tables.

http://www.youtube.com/watch?v=ym_cT2WW4HU&hd=1

http://www.youtube.com/watch?v=Hqcx02AV5Dc&hd=1

Yeah, seems like an odd choice considering Nein beat them 3-0 yesterday

http://logs.tf/171461

This starts in 5 hours time!

Yeah, must suck being such a whiny cunt