StackExchange.DataExplorer
StackExchange.DataExplorer copied to clipboard
StackExchange
Stack Exchange Data Explorer
a \' doesn't escape a ' in a T-SQL string, a double quote does. So the codemirror highlighting needs to honor that. This fixes https://meta.stackexchange.com/questions/350640/backslash-before-single-quote-breaks-syntax-highlighting-the-quote-is-not-escap
this fixes https://meta.stackexchange.com/questions/256042/sede-login-redirects-to-front-page-rather-than-returning I've simply copied the build-up of the returnUrl query parameter as it was done in Views\Account\LogInActiveDirectory.cshtml Tested with the SE OpenId provider. Any other provider that supports...
queries sys.database so might need extra scrutiny for performance before merged because this get called for every fetch on /Index, basically the homepage. This fixes: https://meta.stackexchange.com/questions/315014/improvements-to-data-updated-x-hours-days-ago-message-in-sede
now that most browsers have unicode regex support. Kept backward compatibility with IE11, including broken behavior. This is the second attempt to fix https://meta.stackexchange.com/questions/226703/auto-linkification-of-tags-tagname-fails-when-the-tag-name-contains-nonstandard The earlier PR from Tim is...
Hi everyone, I believe that the "Featured" tab is handled manually. They are very old queries from 2011-2012. I personally prefer to see different queries from time to time. I...
The current implementation of client-side sorting (see issue #19) uses the native JS .sort() method, which is not [stable](https://stackoverflow.com/questions/1517793/what-is-stability-in-sorting-algorithms-and-why-is-it-important) in some browsers (such as, notably, Chrome). This can lead to...
When the Google login got converted from OpenID to OAuth it introduced the big issue of tying the user authentication to the unreliable `User.Email` value, resulting in [instances where the...
Used to be, SEDE would always only link to the query for the site you actually last ran it on in history. That was often useful, but there was also...
It would be nice to allow the BIT type for query parameters, and have it render as a Checkbox on the client side.
