| bio | website | en.wikipedia.org/wiki/… |
|---|---|---|
| location | United Kingdom | |
| age | 25 | |
| visits | member for | 6 months |
| seen | Oct 30 '12 at 22:27 | |
| stats | profile views | 0 |
Pentester, ex-developer, security researcher, reverse engineer, electronics tinkerer, internet activist, zombie eradicator, promulgator of useless facts, shrubbery inspector, bacon aficionado.
Strengths: Security, Crypto, Win32 API, C#, .NET, PHP, x86 assembly
All answers and comments are encrypted with ROT256-ECB.
Opinions are my own. Advice provided with no warranty.
|
Oct 30 |
comment |
Applying user-defined fields to arbitrary entities @HLGEM The problem is with our clients, not the business itself. They operate under some unusual requirements, part of which states that they're not allowed to use any non-vetted software in their production environments. We only just get away with SQL 2008 R2, since they're only officially meant to be using vanilla 2008. |
|
Oct 29 |
comment |
Applying user-defined fields to arbitrary entities @AaronBertrand Sadly the performance of our current approach is horrendous when fetching more than 6 or 7 UDFs, due to the ridiculous number of additional rows produced by JOINs. This gets worse when you try to do any query that involves child entities of two or more distinct entity types and a filter on the UDF value - we end up fetching a gigantic chunk of data and then throw it away in the filter part, because doing it all in one query performs so badly (and often isn't feasible). |
|
Oct 29 |
awarded | Student |
|
Oct 29 |
asked | Applying user-defined fields to arbitrary entities |
|
Oct 29 |
awarded | Autobiographer |
|
Oct 29 |
awarded | Teacher |